[
https://issues.apache.org/jira/browse/DELTASPIKE-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Schneider updated DELTASPIKE-1367:
---------------------------------------
Description:
JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a base
name. This doesn't work for EAR deployments where we must have the DeltaSpike
jars deployed in top-level app lib directory with JNDI resource reference in
application.xml, for which name prefix is java:app/env
Furthermore, it's sometimes desirable to have server-level config, such as for
ProjectStage. For example, a JNDI name
java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be defined
at the server level configuration.
I understand a custom config source can be created to overcome this. However,
the standard JNDI config source should be more flexible.
was:
JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a base
name. This doesn't work for EAR deployments where we must have the DeltaSpike
jars deployed in top-level app lib directory with JNDI resource reference in
application.xml, for which name prefix is java:app/env
Furthermore, it's sometimes desirable to have server-level config, such as for
ProjectStage. For example, a JNDI name
java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be defined
at the server level configuration.
I understand a custom config source can be created to overcome this. However,
the standard JNDI config source should be more flexible. I suggest changing
LocalJndiConfigSource to check
"java:global/env/deltaspike/org.apache.deltaspike/JndiBase" and
"java:app/env/deltaspike/org.apache.deltaspike/JndiBase" and if a value is
found, use that instead of the current BASE_NAME constant value
"java:comp/env/deltaspsike/"
> JNDI Config Source should support alternate JNDI base names
> -----------------------------------------------------------
>
> Key: DELTASPIKE-1367
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1367
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 1.9.0
> Reporter: John Schneider
> Priority: Major
>
> JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a
> base name. This doesn't work for EAR deployments where we must have the
> DeltaSpike jars deployed in top-level app lib directory with JNDI resource
> reference in application.xml, for which name prefix is java:app/env
> Furthermore, it's sometimes desirable to have server-level config, such as
> for ProjectStage. For example, a JNDI name
> java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be
> defined at the server level configuration.
> I understand a custom config source can be created to overcome this.
> However, the standard JNDI config source should be more flexible.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
