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 )
< Development Process in J2EE - J2EE and Test ? >

J2EE and Testing

J2EE Blue Print Program and Compatibility Test

The Application Programming Model specifies neither a mandatory development process nor a specific application architecture. This is not to be understood as a defect because it results from fact that J2EE shell be a "functionally complete architecture".

Especially for the development of webapplication with web components and or EJB a wide range of methodologies and architectural approaches are considered or used. The J2EE blue prints program tries to fill the gap between "every day life development reality" and the highly abstracted programing model.

One building block of the blue print programm is the "petstore"-sample-application. This application acts as a demonstration for the use of recommended practices and patterns in the development process. The suggestions on application architecture, design and deployment made by the blue prints should be considered as practically proven guidelines and recommendations.

The reference implementation completes the J2EE standard by presenting an archetype for J2EE platform that can be used by J2EE Product Providers as well as by the application developers to experience features and behaviour of a standard platform.

Different implementations of the J2EE platform can verify their conformance to the standard by the use of the compatibility test suite. This approach should assure the application developer, that he could run a J2EE compliant application on every J2EE compliant platform.

< Development Process in J2EE - J2EE and Test ? >