OpenEJB -- Open Source EJB Container System

|  |  |  | OpenEJB OpenJMS OpenORB Castor Tyrex |

Main
Welcome!
Download
Mailing Lists
The Team

Users
Quickstart
Hello World!
CMP Example
CMP Guide
Deploy
Startup
Validation
Configuration
Support
Request Feature
FAQ

Servers
Local Server
Remote Server
Tomcat

Integrators
Why OpenEJB
Overview
Design
Specification
Presentation

Developers
Custom Services
Release Plan
Source Code
SourceForge

OpenEJB -- Open Source EJB Container System

## Why OpenEJB?

OpenEJB provides vendors with compliance to the latest EJB specification at a lower opportunity cost than could possibly be achieved by one vendor alone.

Each vendor relying on OpenEJB, in return sponsors development and maintenance on a limited basis. Each vendor also contributes patches, enhancements, or feedback resulting from their own QA testing and customer feedback, leading to a higher quality EJB implementation than is otherwise achievable.

The result is a community implementation of a community defined specification. This leaves your resources free to create QoSs and proprietary technology around and beside the standard technology customers want. The bottom line, increased ability to compete at a lower cost.

OpenEJB is a standard implementation of a standardized technology that companies can leverage to stay with the current market trends while simultaneously focusing internal resources on its own proprietary technologies and unique Quality of Services (QoSs). The risk involved in outsourcing the development of technology is considerably lower when that technology is standardized, all requirements for that technology are completely defined and all design flaws are flushed out before the spec is finalized. While there is some room to provide vendor specific QoSs in a standardized technology like EJB, these are usually minor or side areas leaving the core of the technology rigidly defined. It makes perfect sense to leverage a standard implementation of the core technology, OpenEJB, and instead, focus all internal resources on QoSs and other proprietary technical areas. It makes even more sense when other vendors are sharing in the cost involved to sponsor projects like OpenEJB.

It makes little sense to spend your internal resources implementing your own version of a standardized technology, the customer's view of the technology is also standardized and they will have little reason to choose your implementation over the competition's unless you can offer more QoSs or additional technology or a lower price. Internal resources are better spent focusing one or all three of these areas, compliance with the latest craze technology can be achieved at no internal cost and low financial cost by leveraging OpenEJB.

##

For more information, contact:
David Blevins
OpenEJB Project Lead

Java, EJB, JDBC, JNDI, JTA, Sun, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. XML, XML Schema, XSLT and related standards are trademarks or registered trademarks of MIT, INRIA, Keio or others, and a product of the World Wide Web Consortium. All other product names mentioned herein are trademarks of their respective owners.