You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Jason Porter (Created) (JIRA)" <ji...@apache.org> on 2012/03/23 05:56:22 UTC
[jira] [Created] (DELTASPIKE-128) JNDI lookup for config variables
cannot use java:comp as the sole location
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
[jira] [Resolved] (DELTASPIKE-128) JNDI lookup for config variables
cannot use java:comp as the sole location
Posted by "Gerhard Petracek (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved DELTASPIKE-128.
-----------------------------------------
Resolution: Won't Fix
for now we can use a custom ConfigSource. we might re-visit this topic later on again.
> 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
[jira] [Commented] (DELTASPIKE-128) JNDI lookup for config
variables cannot use java:comp as the sole location
Posted by "Jason Porter (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237780#comment-13237780 ]
Jason Porter commented on DELTASPIKE-128:
-----------------------------------------
If using a custom ConfigSource is the way we want to do that's fine. Just came up as I was writing a blog with an example.
> 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
[jira] [Commented] (DELTASPIKE-128) JNDI lookup for config
variables cannot use java:comp as the sole location
Posted by "Stuart Douglas (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DELTASPIKE-128) JNDI lookup for config
variables cannot use java:comp as the sole location
Posted by "Mark Struberg (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DELTASPIKE-128) JNDI lookup for config
variables cannot use java:comp as the sole location
Posted by "Jason Porter (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236336#comment-13236336 ]
Jason Porter commented on DELTASPIKE-128:
-----------------------------------------
My suggestion is at https://github.com/LightGuard/incubator-deltaspike/tree/DELTASPIKE-128
> 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
[jira] [Closed] (DELTASPIKE-128) JNDI lookup for config variables
cannot use java:comp as the sole location
Posted by "Gerhard Petracek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DELTASPIKE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek closed DELTASPIKE-128.
---------------------------------------
> 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
[jira] [Updated] (DELTASPIKE-128) JNDI lookup for config variables
cannot use java:comp as the sole location
Posted by "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