SourceForge.netOrientation in Objects GmbH
About
Overview
Goals
J2EE and Test
Why frameworks
Tooling philosophy
Future
SourceForge Status
Our SourceForge Site


Products
Recorder
Player
Oracle
Workbench
Ideas


Use
Install
Support for users
Javadocs


Contribute
Work with us
Contact us
) About - J2EE and Test )
< J2EE Platform specification - J2EE Blue Print Program and Compatibility Test >

J2EE and Testing

Development Process in J2EE

It also describes development responsibilities as roles.

  • Services and logic common to many enterprise applications (like transactions, security, rdbms-access...) is provided as integral part of the J2EE platform by the J2EE Product Provider.
  • Application development in the narrow sense is done by the Application Component Provider, the Application Assembler and the Deployer.


The component development process is only specified by its expected outcome components like:

  • Application Components used as Clients that appear to the User similar to native application and are running on local virtual machines.
  • Applets provide a more powerful user interface on the client than simple HTML, running in a browser or specialized container. They are easier to administer and deploy.
  • Web components are Servlets, JSP, Filter or other Java classes running in a webcontainer. They are used to build up HTML or XML output of applications and can be used to construct the middle tier.
  • Enterprise JavaBeans (EJB) that can be used to model the business logic residing in an application. They are running in a special EJB-Container offering transactions, high availibility, scalability, life cycle managment, authentification etc.
<J2EE Platform specification - J2EE Blue Print Program and Compatibility Test >