[jira] [Updated] (DELTASPIKE-128) JNDI lookup for config variables cannot use java:comp as the sole location

["Gerhard Petracek (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek updated DELTASPIKE-128:
----------------------------------------

    Priority: Minor  (was: Major)

changed to minor because it's possible to provide a custom ConfigSource easily.
imo we should only change it, if we find a portable approach for java-se and all java-ee servers (supported by deltaspike).
e.g. recently we saw strange issues with read-only contexts (see http://s.apache.org/3gJ )
                
> JNDI lookup for config variables cannot use java:comp as the sole location
> --------------------------------------------------------------------------
>
>                 Key: DELTASPIKE-128
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-128
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.1-incubating
>         Environment: JBoss AS 7.1.1 possibly other web profile or full profile servers
>            Reporter: Jason Porter
>            Assignee: Gerhard Petracek
>            Priority: Minor
>
> java:comp/env is not available to CDI Extensions in JBoss AS 7.1. I propose we also look under java:global/deltaspike if java:comp/env/deltaspike fails. That would be the next place that would really make sense and an administrator could reliably set without changing a deployment descriptor.

--
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