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

Sagara Gunathunga  commented on AXIS2-5175:
-------------------------------------------

Can you provide a sample and describe exact steps to reproduce this issue ?
                
> serviceTCCL = composite breaks InitialContext lookups inside service code
> -------------------------------------------------------------------------
>
>                 Key: AXIS2-5175
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5175
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.6.0
>         Environment: Tomcat 7.0, axis2 1.6.0, Jdk 1.6.0_29
>            Reporter: Mallik Somepalli
>
> Data source is configured in context.xml and a simple look up in service code 
> for the data source returns with 
> "javax.naming.NameNotFoundException: Name java:comp is not bound in this 
> Context"
> On initial glance, this seem to be caused by getParent() method 
> "org.apache.axis2.classloader.MultiParentClassLoader" not returning parent 
> class loader properly. Tomcat keeps track of jndi bindings per class 
> loader/per thread and when serviceTCCL is configured, the bindings are not 
> found context of MultiParentClassLoader or its parent chain (getParent breaks 
> the chain).The java doc on this class says "This getParent method of this 
> class will always return null, which may be interpreted by the calling code 
> to mean that this class loader is a direct child of the system class". 

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to