[OPENEJB-125] ejb-jar scoped JNDI ENC

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.x
• Fix Version/s: 3.1.x
• Component/s: container system, deployment
• Assignee: Unassigned
• Reporter: David Blevins
• Due: 25/Sep/06
• Created: 16/Feb/06 16:37
• Updated: 17/Jul/12 07:09
• Resolved: 17/Jul/12 07:09

Description

Support for an ejb-jar level JNDI ENC that all ejbs in an ejb-jar can share. The individual JNDI ENC of a bean would override the ejb-jar level ENC the resulting ENC is available to each bean as their ENC.

This could be configured in the bottom of the assembly-decsriptor element of the ejb-jar.xml as an zero or more.

<assembly-descriptor>
...
<env-entry>
<env-entry-name>defaultDateFormat</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>YY-MM-DD</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>regionalCurrency</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>USD</env-entry-value>
</env-entry>
</assembly-descriptor>

People who do any real work with JNDI end up specifying a few JNDI entries over and over again in an ejb-jar which is really annoying. Those that don't want to go that route attempt to use hacks to try and reference properties files on the system.