[DELTASPIKE-1367] JNDI Config Source should support alternate JNDI base names

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.9.0
• Component/s: Configuration
• Assignee: Mark Struberg
• Reporter: John Schneider
• Created: 08/Jan/19 00:30
• Updated: 10/Nov/19 19:01
• Resolved: 10/Nov/19 19:01

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.