Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added more features

...

JAX-WS and CORBA support will be added in future releases. Support for the JAX-RPC API is not a planned feature.

EJB Plugin for Tomcat 6

OpenEJB 3.0 can be plugged into any Tomcat 6 server, adding support for EJBs in Web Apps. War files themselves can contain EJBs and the Servlets can use new JavaEE 5 annotations, XA transactions, JPA, and JMS. Webapps can even support fat java clients connecting over HTTP.

CMP via JPA

Our CMP implementation is a thin layer over the new Java Persistence API (JPA). This means when you deploy an old style CMP 1.1 or CMP 2.1 bean it is internally converted and ran as a JPA bean. This makes it possible to use both CMP and JPA in the same application without any coherence issues that can come from using two competing persistence technologies against the same data. Everything is ultimately JPA in the end.

...

Validation output comes in three levels. The most verbose level will tell you in detail what you did wrong, what the options are, and what to do next... even including valid code and annotation usage tailored to your app that you can copy and paste into your application. Very ideal for beginners and people using OpenEJB in a classroom setting.

JNDI Name Formatting

A complication when using EJB is that plain client applications are at the mercy of vendor's chosen methodology for how JNDI names should be constructed. OpenEJB breaks the mold by allowing you to specify the exact format you'd like OpenEJB to use for your server or any individual application. Supply us with a formatting string, such as "ejb/{ejbName}/{interfaceClass.simpleName}", to get a JNDI layout that best matches your needs.

Changelog

Wiki Markup
{swizzlejira}
#set ( $jira = $rss.fetch("http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=12310530&status=5&status=6&fixfor=12312075&tempMax=1000&reset=true&decorator=none") )
#set( $issues = $jira.issues )

h3. New Features:

{swizzlejiraissues:issues=$as.param($issues.equals("type", "New Feature").descending("id"))|columns=key;summary}

h3. Improvements:

{swizzlejiraissues:issues=$as.param($issues.equals("type", "Improvement"))|columns=key;summary}

h3. Tasks & Sub-Tasks:

{swizzlejiraissues:issues=$as.param($issues.matches("type", "Task|Sub-task").sort("summary"))|columns=key;summary}

h1. Unimplemented Features, bugs, limitations

#set ( $jira = $rss.fetch("http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=12310530&status=1&status=3&status=4&version=12312075&tempMax=1000&reset=true&decorator=none") )
#set( $issues = $jira.issues )

{swizzlejiraissues:issues=$as.param($issues.sort("priority"))|columns=key;summary}

{swizzlejira}