In order to achieve compliancy with the EJB 3.1 global JNDI namespace requirements, the "app-name" of an application (.ear packaged) must be made available to org.apache.openejb.assembler.classic.JndiBuilder. In my opinion, this would be best achieved by setting applicationID (a new property) in DeploymentInfo (and as a consequence, CoreDeploymentInfo).
I will also add a new JNDI template parameter, applicationId.

I'm still trying to locate the part in org.apache.openejb.assembler.classic.Assembler that deploys an .ear package. I just have to say that this class (among some others) is a mess. It's a mish-mash of fields and methods here and there with little to no documentation or organization. I think some kind of mutually agreed coding standards would certainly help hold this project together and decrease the learning curve for newbies (such as myself).

Reply via email to