[
https://issues.apache.org/jira/browse/OPENEJB-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Louis MONTEIRO closed OPENEJB-125.
---------------------------------------
Resolution: Fixed
Works
> ejb-jar scoped JNDI ENC
> -----------------------
>
> Key: OPENEJB-125
> URL: https://issues.apache.org/jira/browse/OPENEJB-125
> Project: OpenEJB
> Issue Type: Wish
> Components: container system, deployment
> Affects Versions: 3.1.x
> Reporter: David Blevins
> Fix For: 3.1.x
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
