[infinispan-issues] [JBoss JIRA] (ISPN-7036) Resolve classes properly when EmbeddedContextClassResolver is initialized with null

[Thomas Segismont (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13297840#comment-13297840 ] 

Thomas Segismont commented on ISPN-7036:
----------------------------------------

[~dan.berindei] I think that when the TCCL is null, yes, we should assume application classes are in the same classloader as the ISPN classes. It is in the contract of Thread#getContextClassloader to [possibly return null|https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.html#getContextClassLoader--]

> Resolve classes properly when EmbeddedContextClassResolver is initialized with null
> -----------------------------------------------------------------------------------
>
>                 Key: ISPN-7036
>                 URL: https://issues.jboss.org/browse/ISPN-7036
>             Project: Infinispan
>          Issue Type: Bug
>            Reporter: Sebastian Łaskawiec
>
> Some applications set the main thread context classloader to null. This breaks the ISPN class resolver chain (EmbeddedContextClassResolver initialized with null classloader)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)