blog = http://acme.org/myblog
birthday = locale=en_US style=MEDIUM Mar 1, 1954
homeDirectory = /home/esmith/
## Support for GlassFish descriptors
Unit testing EJBs with OpenEJB is a major feature and draw for people, even
for people who may still use other app servers for final deployment such as
Geronimo or GlassFish. The descriptor format for Geronimo is natively
understood by OpenEJB as OpenEJB is the EJB Container provider for
Geronimo. However, OpenEJB also supports the GlassFish descriptors so
people using GlassFish as their final server can still use OpenEJB for
testing EJBs via plain JUnit tests in their build and only have one set of
vendor descriptors to maintain.
## JavaEE 5 EAR and Application Client support
JavaEE 5 EARs and Application Clients can be deployed in addition to ejb
jars. EAR support is limited to ejbs, application clients, and libraries;
WAR files and RAR files will be ignored. Per the JavaEE 5 spec, the
META-INF/application.xml and META-INF/application-client.xml files are
optional.
## Application Validation for EJB 3.0
Incorrect usage of various new aspects of EJB 3.0 are checked for and
reported during the deployment process preventing strange errors and
failures.
As usual validation failures (non-compliant issues with your application)
are printed out in complier-style "all-at-once" output allowing you to see
and fix all your issues in one go. For example, if you have 10
@PersistenceContext annotations that reference an invalid persistence unit,
you get all 10 errors on the *first* deploy rather than one failure on the
first deploy with 9 more failed deployments to go.
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](openejbx30:jndi-names.html)
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
{swizzlejira}
1. 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")
)
1. set( $issues = $jira.issues )
### New Features:
{swizzlejiraissues:issues=$as.param($issues.equals("type", "New
Feature").descending("id"))|columns=key;summary}
### Improvements:
{swizzlejiraissues:issues=$as.param($issues.equals("type",
"Improvement"))|columns=key;summary}
### Tasks & Sub-Tasks:
{swizzlejiraissues:issues=$as.param($issues.matches("type",
"Task|Sub-task").sort("summary"))|columns=key;summary}
# Unimplemented Features, bugs, limitations
1. 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")
)
1. set( $issues = $jira.issues )
{swizzlejiraissues:issues=$as.param($issues.sort("priority"))|columns=key;summary}
{swizzlejira}