September 2001
Intermediate to advanced
592 pages
18h 22m
English
Content preview from Enterprise JavaBeans, Third EditionBecome 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,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
J2EE Fills in the Gaps
The J2EE specification attempts to fill the gaps between the web components and Enterprise JavaBeans by defining how these technologies come together to form a complete platform.
One of the ways in which J2EE adds value is by creating a consistent
programming model across web components and enterprise beans through
the use of the JNDI ENC and XML deployment descriptors. A servlet in
J2EE can access JDBC DataSource objects,
environment entries, and references to enterprise beans through a
JNDI ENC in exactly the same way that enterprise beans use the JNDI
ENC. To support the JNDI ENC, web components have their own XML
deployment descriptor that declares elements for the JNDI ENC
(<ejb-ref>,
<resource-ref>,
<env-entry>) as well security roles and
other elements specific to web components. In J2EE, web components
are packaged along with their XML deployment descriptors and deployed
in JAR files with the extension
.war, which
stands for web archive. The
use of the JNDI ENC, deployment descriptors, and JAR files in web
components makes them consistent with the EJB programming model and
unifies the entire J2EE platform.
Use of the JNDI ENC makes it much simpler for web components to
access Enterprise JavaBeans. The web component developer does not
need to be concerned with the network location of enterprise beans;
the server will map the <ejb-ref> elements
listed in the deployment descriptor to the enterprise beans at
deployment time.
Optionally, J2EE vendors can ...
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
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.