On Sep 27, 2007, at 12:24 AM, David Blevins wrote:
On Sep 27, 2007, at 12:00 AM, Dario Laverde wrote:
Ok, so with Java 5, OpenJPA requires the agent and OpenEJB
currently only supports
OpenJPA as the JPA provider correct?
True for the first part. For the second part, any compliant JPA
provider should work. The only thing we'd still require OpenJPA
for is to support CMP, but if you don't use them you're fine; just
make sure you delete the cmp container declaration from the conf/
openejb.xml file so that container won't load.
Our CMP implementation is 95% JPA generic and about 5% OpenJPA
specific. Even then we could support other JPA impls provided we
could get the right hooks.
The limiting factory is my attention span. Currently, Tomcat is the
shiny ball :)
I also noticed you added security servlets in the latest ejb-
examples, so EJB
security in Tomcat now works?
Neat! Interested in that answer as well :)
Yep. In trunk OpenEJB uses the Tomcat realm for authentication and
authorization. Basically, we inherit the login from the web
application. If you invoke an EJB directly using a remote client,
then we use the realm in the first Tomcat engine.
This is the first big beta-2 feature on the books :)
-dain
