Getting Started with Enterprise Java Beans (EJB) 3.0
There are significant differences between earlier versions of Enterprise Java Beans (EJB) and EJB 3.0. At least some of these pertain to business components. EJB 3.0 makes it a lot easier to implement the complexity required by many enterprises in fewer steps. Keep reading to learn more.
Getting Started with Enterprise Java Beans (EJB) 3.0 (Page 1 of 4 )
Each enterprise has its own set of business rules. These rules are formed around the enterprise's particular business model. This means that any application targeting enterprises should be capable of implementing business rules.
That is where business components come into the picture. As these components form the backbone of any enterprise level application, their requirements also vary. The requirements include security, robustness and fail-safety to name a few. These are some of the services that are provided by the EJB container to the EJB, which is the business component in the world of JEE.
However there is a major limitation with EJBs - complexity. Even for an EJB encapsulating a simple logic, many steps must be followed. Understanding this limitation, a new version of EJB has been introduced. The concepts introduced in this version totally change the development cycle involved in developing EJB.
In this article, I will be focusing on the basics required to start developing EJB according to EJB 3.0. The first section will cover the differences between EJB 2.1 and EJB 3.0. In the second section I will enumerate the steps in migrating from EJB 2.1 to EJB 3.0 using Session Beans as an example. In the third section I will develop a Stateless Session Bean according to the steps enumerated in the second section and client accessing it. That is the agenda for this discussion.