Architectural Overview: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
'''The Enterprise JavaBeans (EJB) architecture has the following goals:''' |
'''The Enterprise JavaBeans (EJB) architecture has the following goals:''' |
||
* The Enterprise JavaBeans architecture will be the standard component architecture for building |
* [The Enterprise JavaBeans architecture will be the standard component architecture for building |
||
distributed object-oriented business applications in the Java™ programming language. |
distributed object-oriented business applications in the Java™ programming language.] |
||
* The Enterprise JavaBeans architecture will support the development, deployment, and use of |
* The Enterprise JavaBeans architecture will support the development, deployment, and use of |
||
web services. |
web services. |
Revision as of 15:46, 19 November 2004
The Enterprise JavaBeans (EJB) architecture has the following goals:
- [The Enterprise JavaBeans architecture will be the standard component architecture for building
distributed object-oriented business applications in the Java™ programming language.]
- The Enterprise JavaBeans architecture will support the development, deployment, and use of
web services.
- The Enterprise JavaBeans architecture will make it easy to write applications: Application
developers will not have to understand low-level transaction and state management details, multi-threading, connection pooling, or other complex low-level APIs.
- Enterprise JavaBeans applications will follow the Write Once, Run Anywhere™ philosophy of
the Java programming language. An enterprise bean can be developed once, and then deployed on multiple platforms without recompilation or source code modification.
- The Enterprise JavaBeans architecture will address the development, deployment, and runtime
aspects of an enterprise application’s life cycle.