Uploaded image for project: 'DeltaSpike'
  1. DeltaSpike
  2. DELTASPIKE-1367

JNDI Config Source should support alternate JNDI base names

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.9.0
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None

      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.

       

        Attachments

          Activity

            People

            • Assignee:
              struberg Mark Struberg
              Reporter:
              JohnSchneider John Schneider
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: