cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaitanya Choleti (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2085) Applications classloader should be set during method invocations.
Date Tue, 10 Mar 2009 10:40:50 GMT

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

Chaitanya Choleti commented on CXF-2085:
----------------------------------------

You are right, we can use User.class.getClassLoader() , but the application developer need
not know how CXF works and may use Thread.currentThread().getContextClassLoader() . But I
guess that is not your problem.

Thanks for the help.

> 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
>
>         Attachments: cl_test.war, new_cl_test.war, new_sources.zip, sources.zip
>
>
> 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.


Mime
View raw message