THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Over the years, OpenEJB has innovated the art of the embedded/Java SE EJB container usable as a plain library much the way an embedded databases work. In a simple 1, 2, 3 step of 1) add OpenEJB to your classpath, 2) add a META-INF/ejb-jar.xml containing at minimum "<ejb-jar/>", then 3) use the org.apache.openejb.client.LocalInitialContextFactory when creating your client InitialContext, you've got a Java SE EJB container that can be used in unit tests, your IDE, or anyway you'd like to drop in EJB functionality. Configuration can be done through an openejb.xml file or can be encapsulated 100% in the test case through the parameters passed to the InitialContext. For example, to create a JTA DataSource for JPA usage, you can simply:
...
See the examples zip for a dozen embedded testing examples that range from simple @Stateless beans to advanced transaction and security testing.
...
OpenEJB 3.0 supports injection of any data type for which you can supply a JavaBeans PropertyEditor. We include several built-in PropertyEditors already such as Date, InetAddress, Class, File, URL, URI, Map, List, any java.lang.Enum and more.
...
...
Dependency Injection – Generic Collections and Maps
Support for Java Generics makes the dependency injection that much more powerful. Declare an injectable field that leverages Java Generics and we will use that information to boost your injection to the next level. For example:
...
...
Dependency Injection – Custom Types
You can easily add your own types or override the way built-in types are handled and claim dependency injection as your own making it a critical part of your architecture. For example, let's register a custom editor for our Pickup enum.
...
...
The META-INF/env-entries.properties
...
To fix this, OpenEJB supports the idea of a META-INF/env-entries.properties file where we will look for the value of things that need injection that are not container controlled resources (i.e. datasources and things of that nature). You can configure you ejbs via a properties file and skip the need for an ejb-jar.xml and it's 5 lines per property madness.
...
Support for GlassFish descriptors
...
Some example output might look like the following. Here we illegally add some annotations to the "Movies" bean's interface as well as use the wrong annotations for various types of injection:
...
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.
...