deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart Douglas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DELTASPIKE-128) JNDI lookup for config variables cannot use java:comp as the sole location
Date Fri, 23 Mar 2012 05:00:22 GMT

    [ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236326#comment-13236326
] 

Stuart Douglas commented on DELTASPIKE-128:
-------------------------------------------

The reason why java:comp is not available is because in  a multi-war ear there are multiple
java:comp name spaces available (and in an ear without a war there are none), so relying on
java:comp being present is non-portable. 
                
> 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
>
> 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

        

Mime
View raw message