[
https://issues.apache.org/jira/browse/GERONIMO-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-4630:
-----------------------------------
Component/s: (was: general)
naming
Support for overriding in geronimo plans was already implemented for 2.1.4 and
2.2, see GERONIMO-3954
We need to check this works for openejb, as noted there.
However as noted here we need something even more flexible.
> Need good ways to override env-entry values in jndi
> ---------------------------------------------------
>
> Key: GERONIMO-4630
> URL: https://issues.apache.org/jira/browse/GERONIMO-4630
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: naming
> Reporter: David Jencks
>
> Currently we have no way to override env-entry values supplied in spec
> deployment descriptors or annotations.
> Minimally we need to be able to override them in geronimo plans, I think
> there's already a jira for that.
> However people may want to set these from some kind of global configuration
> file for the server. We need to think up a way to do something like this.
> One possibility -- not sure how good it is -- would be to have the geronimo
> plan configure jndii links to global jndi. Then you can put whatever you
> want in global jndi such as by reading in a property file using a gbean and
> binding stuff.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
