Architectural Overview: Difference between revisions

From
Jump to navigation Jump to search
No edit summary
No edit summary
 
(7 intermediate revisions by one other user not shown)
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
----
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 be the standard component architecture for building distributed object-oriented business applications in the Java™ programming language.
web services.
* The Enterprise JavaBeans architecture will make it easy to write applications: Application
*The Enterprise JavaBeans architecture will support the development, deployment, and use of web services.
developers will not have to understand low-level transaction and state management details,
*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.
multi-threading, connection pooling, or other complex low-level APIs.
* Enterprise JavaBeans applications will follow the Write Once, Run Anywhere™ philosophy of
*The Enterprise JavaBeans architecture will address the development, deployment, and runtime aspects of an enterprise application’s life cycle.
*The Enterprise JavaBeans architecture will define the contracts that enable tools from multiple vendors to develop and deploy components that can interoperate at runtime.
the Java programming language. An enterprise bean can be developed once, and then
*The Enterprise JavaBeans architecture will make it possible to build applications by combining components developed using tools from different vendors.
deployed on multiple platforms without recompilation or source code modification.
* The Enterprise JavaBeans architecture will address the development, deployment, and runtime
*The Enterprise JavaBeans architecture will provide interoperability between enterprise beans and Java 2 Platform, Enterprise Edition (J2EE) components as well as non-Java programming language applications.
*The Enterprise JavaBeans architecture will be compatible with existing server platforms. Vendors will be able to extend their existing products to support Enterprise JavaBeans.
aspects of an enterprise application’s life cycle.
*The Enterprise JavaBeans architecture will be compatible with other Java programming language APIs.
⚫
*The Enterprise JavaBeans architecture will be compatible with the CORBA protocols.

----
----


*[[Enterprise Bean Componenten]]
*[[The Enterprise Bean Components]]
*[[Classes and Interfaces (Remote/Home)]]
*[[Classes and Interfaces (Remote/Home)]]
*[[Deployment Descriptor (DD)]]
*[[Deployment Descriptor (DD)]]

Latest revision as of 08:56, 8 February 2005

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.
  • The Enterprise JavaBeans architecture will define the contracts that enable tools from multiple vendors to develop and deploy components that can interoperate at runtime.
  • The Enterprise JavaBeans architecture will make it possible to build applications by combining components developed using tools from different vendors.
  • The Enterprise JavaBeans architecture will provide interoperability between enterprise beans and Java 2 Platform, Enterprise Edition (J2EE) components as well as non-Java programming language applications.
  • The Enterprise JavaBeans architecture will be compatible with existing server platforms. Vendors will be able to extend their existing products to support Enterprise JavaBeans.
  • The Enterprise JavaBeans architecture will be compatible with other Java programming language APIs.
  • The Enterprise JavaBeans architecture will be compatible with the CORBA protocols.
Retrieved from "https://sarwiki.informatik.hu-berlin.de/index.php?title=Architectural_Overview&oldid=3124"