Hi Thomas, here are few pointers:
- http://tomee.apache.org/documentation.old.html is the old doc page (hopefully pretty useless now or soon) - testing portal is there http://tomee.apache.org/developer/testing/index.html. You see to be in http://tomee.apache.org/developer/testing/other/index.html case but other ones can be interesting too depending your plans - configuration portal is http://tomee.apache.org/admin/configuration/index.html and I think you mainly want to have a look to http://tomee.apache.org/admin/configuration/resources.html. You can feel like datasource properties are missing but if you read the high level explanation + datasource part you will see you just need to refer to the implementation we use (tomcat-jdbc or dbcp2) page for that. When migrating/enhancing this page I got rid of datasource specific properties which is not something tomee owns cause of that behavior but just referenced where to find them up to date Hope it helps Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-01-27 2:31 GMT+01:00 Thomas Whitmore <twhitm...@bravurasolutions.com>: > 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 > ______________________________________________________________________
