[
https://issues.apache.org/jira/browse/DELTASPIKE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-339.
--------------------------------------
Resolution: Fixed
we do. As per the general ConfigSource notion that JNDI is part of the
Configuration which will get scanned automatically. If it is not active it
would not be possible to use JNDI to e.g. configure globalAlternatives.
> JndiUtils is broken
> -------------------
>
> Key: DELTASPIKE-339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-339
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.4-incubating
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Blocker
> Fix For: 0.4-incubating
>
>
> A recent change in JndiUtils caused a bug in a few Containers
> java.lang.IllegalStateException: Could not get java:comp/ORB from JNDI
> at
> org.apache.deltaspike.core.impl.util.JndiUtils.lookup(JndiUtils.java:79)
> at
> org.apache.deltaspike.core.impl.util.JndiUtils.list(JndiUtils.java:186)
> at
> org.apache.deltaspike.test.core.impl.util.JndiUtilsTest.testList(JndiUtilsTest.java:72)
> The code currently enlists all registered objects in JNDI java:comp and tries
> to lookup() them as a specific type. But as per the spec of
> javax.naming.Context this will always throw a javax.naming.NamingException if
> the type of the registered object in JNDI does not match the type for the
> bind() operation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
