geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-2787) Usability: jndi name collision error not reported
Date Wed, 31 Jan 2007 20:24:05 GMT
Usability: jndi name collision error not reported
-------------------------------------------------

                 Key: GERONIMO-2787
                 URL: https://issues.apache.org/jira/browse/GERONIMO-2787
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: naming
            Reporter: Jarek Gawor


I defined the following entries in my web.xml file:

   <service-ref>
       <service-ref-name>services/myService/foo</service-ref-name>
       <service-interface>foo</service-interface>
   </service-ref>
   <service-ref>
       <service-ref-name>services/myService</service-ref-name>
       <service-interface>bar</service-interface>
   </service-ref>

So the JNDI mapping where: 'java:comp/env/services/myService/foo' = serviceRef1 and  'java:comp/env/services/myService'
= serviceRef2

That caused the following exception:

java.lang.ClassCastException: org.apache.xbean.naming.reference.CachingReference

        at org.apache.xbean.naming.context.ContextUtil.buildMapTree(ContextUtil.
java:286)
        at org.apache.xbean.naming.context.ContextUtil.createBindings(ContextUti
l.java:231)
        at org.apache.xbean.naming.context.ImmutableContext.<init>(ImmutableCont
ext.java:53)
        at org.apache.xbean.naming.context.ImmutableContext.<init>(ImmutableCont
ext.java:39)
        at org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpri
seNamingContext(EnterpriseNamingContext.java:75)
        at org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpri
seNamingContext(EnterpriseNamingContext.java:71)
        at org.apache.geronimo.cxf.CXFWebServiceContainerFactoryGBean.<init>(CXF
WebServiceContainerFactoryGBean.java:66)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

The second JNDI name cannot be used because 'myService' is a sub context. However, this is
not checked and that strange exception is raised.

  





-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message