Hi everybody,

We're prototyping OpenEJB as an embedded container to support the portion of 
our unit-testing which needs EJB functionality. So far it seems a good clean 
component, working well for us. Nice quality of code under the covers, too.

In particular one feature we like is  the ability to configure OpenEJB 
dynamically (Datasources etc) via the properties. Since we have datasource 
config varying between developer environments, and another primary place 
already exists for configuration,  it's nice not to need configuration 
duplicated (and developers to have to change it manually) to support the 
OpenEJB modality of running unit-tests.

We use embedded container startup & restriction of which classpath roots to 
scan:

-          properties.setProperty("openejb.deployments.classpath.include", 
"(.*moduleWithEjbs/target/classes/)");

-          EJBContainer.createEJBContainer(properties);
We also use property-driven configuration:  eg.

-          properties.setProperty( "TransactionManager", 
"new://TransactionManager/");

-          properties.setProperty( "java:/MyDatasource", 
"new://Resource/?type=java.sql.DataSource"+params);

Since these two capabilities benefitted us but the areas not so well 
documented, I'd like to ask about potentially contributing a little 
documentation in the area 1) of how to startup an embedded OpenEJB container 
and 2) property-based configuration.

There's also 3) the rather outstanding issue of the empty 'Documentation' page 
on the "new" TomEE site.  Does anybody have a list of what of the old doco is 
still valid/ and what's outdated? If a quick usable TOC could be put up, that 
would be far better than having just an empty page; and would enable 
'Documentation' to be added to the site navbar (hard to find currently).

I won't have a lot of time, but if there's some improvement that can be 
achieved in a few hours I'd like to consider it.

Thoughts?

Regards,
Thomas

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

Reply via email to