On Nov 2, 2007, at 12:52 PM, David Blevins wrote:
On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote:
We are using the <local-jndi-name> tags to force a JNDI name in
our weblogic-ejb-jar.xml file. Openejb appears to allow the same
tag in the openejb-jar.xml, but seems to ignore it completely.
We don't quite have the same tag in the openejb-jar.xml. You've
hit upon one of the only remaining todos, let me see if i can hack
something up for you. Ideally we should support your weblogic-ejb-
jar.xml directly so you don't have to maintain an openejb-jar.xml
file.
Ok, I've added the support we've been needing for per ejb jndi names:
http://issues.apache.org/jira/browse/OPENEJB-253
Note that you can still use a template if you like, i.e. "ejb/
org.superbiz.Foo" works or you can just "ejb/{interfaceClass}".
Then I also hooked up support for pulling the jndi names out of the
weblogic-ejb-jar.xml file also, so you really don't need to bother
with an openejb-jar.xml. The wls conversion code so far only supports
<jndi-name> and <local-jndi-name>. It'll take a bit to add cmp
conversion (we use JPA for our CMP), but by the looks of the entity
you posted, it should work fine as-is because the field names match
the column names which is JPA default.
Back on the subject of JNDI names, do you happen to know the jndi
format WebLogic uses for EJB 3 business interfaces? I poked around but
didn't find anything definitive, got the impression they were just
using interface name. I'd like to adjust the default template
appropriately to match.
New snapshots have been published. Just switch your dependency
version to 3.0.0-SNAPSHOT, give it a try and let us know if it works.
-David