Enterprise JavaBeans
Enterprise JavaBeans is a very big topic, and we can’t do more than provide a few paragraphs to whet your appetite. If you want more information, see Enterprise JavaBeans by Richard Monson-Haefel (O’Reilly & Associates). The thrust of EJB is to take the JavaBeans philosophy of portable, pluggable, components and extend it to accommodate the sorts of things that three-tiered networked and database-centric applications require. Although EJB is built on the basic JavaBeans concepts, it is much larger and more “special-purpose.” It doesn’t have a lot in common with the kinds of things we’ve been talking about in this chapter. EJBs are primarily server-side components for networked applications. Sun’s Forte development environment, among others, provides some support for working with Enterprise JavaBeans.
EJB ties together a number of other Java “enterprise"-oriented APIs, including database access, transactions, and name services, into a single component model for server applications. EJB imposes a lot more structure on how you write code than plain old JavaBeans. But it does so in order to allow the server-side EJB container to take on a lot of responsibility for you and to optimize your application’s activities without you having to write a lot of code. Here are a few of the things that Enterprise JavaBeans tackles:
Object lifecycle and name service lookup
Container-managed persistence
Transaction management
Server resource pooling and management
Deployment configuration ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access