[
https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236352#comment-13236352
]
Mark Struberg commented on DELTASPIKE-128:
------------------------------------------
Well, if we start messing around with JNDI that way, then we need to make it
completely flexible. I know of no single EE container where JNDI is _not_
completely fuuuuu up...
We need a way to configure the JNDI lookup paths in a flexible way.
As we are on the 'JNDI is broken' topic: do we also put stuff into JNDI
somewhere in DeltaSpike? Because finding a reliably writable JNDI location is
another mess...
> 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
