You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2009/03/05 20:39:56 UTC

[jira] Commented: (CXF-2085) Applications classloader should be set during method invocations.

    [ https://issues.apache.org/jira/browse/CXF-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679319#action_12679319 ] 

Sergey Beryozkin commented on CXF-2085:
---------------------------------------

Hi

Can you provide some simple test case please ? I'm not sure I understand. If a class lazily loaded when one of the resource class methods is being invoked then the resource class loader will be used to load the class first... 

 

> Applications classloader should be set during method invocations.
> -----------------------------------------------------------------
>
>                 Key: CXF-2085
>                 URL: https://issues.apache.org/jira/browse/CXF-2085
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Chaitanya Choleti
>             Fix For: 2.2
>
>
> Invocation of a JAX-RS method may depend on some application classes which may not be loaded already, they will be loaded during invocation. But during invocation the classloader will be CXF war application classloader, this will lead to NoClassDefFoundErrors. To avoid this root resource class' classloader should be set on the current thread.
> Similar fix should be applied to provider methods such as readFrom, writeTo etc.

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