 - Enterprise JavaBeans (EJB) is an architecture for setting up program components, written in the Java programming language, that run in the server parts of a computer network that uses the client/server model. Enterprise JavaBeans is built on the JavaBeans technology for distributing program components (which are called Beans, using the coffee metaphor) to clients in a network. Enterprise JavaBeans offers enterprises the advantage of being able to control change at the server rather than having to update each individual computer with a client whenever a new program component is changed or added. EJB components have the advantage of being reusable in multiple applications. To deploy an EJB Bean or component, it must be part of a specific application, which is called a container.
Originated by Sun Microsystems, Enterprise JavaBeans is roughly equivalent to Microsoft's Component Object Model/Distributed Component Object Model architecture, but, like all Java-based architectures, programs can be deployed across all major operating systems, not just Windows. EJB's program components are generally known as servlets (little server programs). The application or container that runs the servlets is sometimes called an application server. A typical use of servlets is to replace Web programs that use the common gateway interface (CGI) and a Practical Extraction and Reporting Language script. Another general use is provide an interface between Web users and a legacy application mainframe application and its database.
In Enterprise JavaBeans, there are two types of beans: session beans and entity beans. An entity bean is described as one that, unlike a session bean, has persistence and can retain its original behavior or state.
 |
Learn more about Java Web Services |
| JavaOne: JBoss on SOA middleware, Java EE and data services: Is SOA middleware that different from traditional middleware? At JavaOne, Red Hat's Craig Muzilla ponders that and the future of Java EE and data services. |
| Java One: Mule architect looks to bring REST to SOA: In a conversation at JavaOne, MuleSource's Dan Diephouse, talks about his work on Mule Galaxy, the REST-based open source registry/repository that is going GA later this month. |
| Mule architect sees REST with Atom rising, UDDI fading: Dan Diephouse, the creator of XFire and software architect at MuleSource Inc., discusses the advantages in using REST and the Atom Publishing Protocol. |
| Oracle links SOA, data services, BI and BAM: When it comes to incorporating data services, business intelligence (BI), and business activity monitoring (BAM), Oracle has not lost sight of its database roots. |
| Eclipse, Sun and Oracle team up on persistence API: The surprise announcement from EclipseCon, is Sun Microsystems. selecting the Oracle led EclipseLink project as the reference implementation for the Java Persistence API 2.0. |
| JavaOne news: A collection of SOA and Web services news related articles from the JavaOne conference held in San Francisco. |
| 2006 JavaOne coverage: A compilation of stories written about the JavaOne conference held in San Francisco this past May. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: Working with Beehive Web services and JSR 181: This chapter, excerpted from Pro Apache Beehive, explores the Web service capabilities that are a part of Apache Beehive. You'll learn about JSR 181, Web Services Metadata for the Java ... |
| Decision time: .NET or J2EE?: How do .NET and J2EE stack up against one another? That depends on who you ask. We've compiled resources from both sides of the fence to help you decide for yourself. |
| CONTRIBUTORS: |
Hayden Marchant |
| LAST UPDATED: |
24 Mar 2003
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
