You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Mike Rheinheimer (JIRA)" <ji...@apache.org> on 2007/07/10 20:06:05 UTC
[jira] Created: (AXIS2-2935) Set async callback ClassLoader to the
original client's ClassLoader
Set async callback ClassLoader to the original client's ClassLoader
-------------------------------------------------------------------
Key: AXIS2-2935
URL: https://issues.apache.org/jira/browse/AXIS2-2935
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Mike Rheinheimer
Assignee: Mike Rheinheimer
Fix For: nightly
(All credit for this Jira goes to Nick Gallardo, including the below text, and attached patch.)
With some QoSes applied, the thread that JAX-WS gets to process the response on does not have the appropriate ClassLoader
setup. It has the same content, but is a different instance which results in a ClassCastException when we try to unmarshall
the response content with JAXB.
The fix is to set the Thread's context ClassLoader to same one that was used to load the AsyncHandler callback class.
That ensures we have both the right content and the right instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2935) Set async callback ClassLoader to the
original client's ClassLoader
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer updated AXIS2-2935:
------------------------------------
Attachment: patch_555023_555024.txt
> Set async callback ClassLoader to the original client's ClassLoader
> -------------------------------------------------------------------
>
> Key: AXIS2-2935
> URL: https://issues.apache.org/jira/browse/AXIS2-2935
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Mike Rheinheimer
> Assignee: Mike Rheinheimer
> Fix For: nightly
>
> Attachments: patch_555023_555024.txt
>
>
> (All credit for this Jira goes to Nick Gallardo, including the below text, and attached patch.)
> With some QoSes applied, the thread that JAX-WS gets to process the response on does not have the appropriate ClassLoader
> setup. It has the same content, but is a different instance which results in a ClassCastException when we try to unmarshall
> the response content with JAXB.
> The fix is to set the Thread's context ClassLoader to same one that was used to load the AsyncHandler callback class.
> That ensures we have both the right content and the right instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2935) Set async callback ClassLoader to the
original client's ClassLoader
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer resolved AXIS2-2935.
-------------------------------------
Resolution: Fixed
Fixed in 555024
> Set async callback ClassLoader to the original client's ClassLoader
> -------------------------------------------------------------------
>
> Key: AXIS2-2935
> URL: https://issues.apache.org/jira/browse/AXIS2-2935
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Mike Rheinheimer
> Assignee: Mike Rheinheimer
> Fix For: nightly
>
> Attachments: patch_555023_555024.txt
>
>
> (All credit for this Jira goes to Nick Gallardo, including the below text, and attached patch.)
> With some QoSes applied, the thread that JAX-WS gets to process the response on does not have the appropriate ClassLoader
> setup. It has the same content, but is a different instance which results in a ClassCastException when we try to unmarshall
> the response content with JAXB.
> The fix is to set the Thread's context ClassLoader to same one that was used to load the AsyncHandler callback class.
> That ensures we have both the right content and the right instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org