You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2010/07/12 20:31:50 UTC
[jira] Created: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
-------------------------------------------------------------------------------------
Key: AXIS2-4774
URL: https://issues.apache.org/jira/browse/AXIS2-4774
Project: Axis2
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
History:
The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
Problem:
If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
Solution:
The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4774.
-----------------------------------
Resolution: Fixed
submitted revision 963419
> JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-4774
> URL: https://issues.apache.org/jira/browse/AXIS2-4774
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> History:
> The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
> Problem:
> If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
> Solution:
> The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
> If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4774.
-----------------------------------
Resolution: Fixed
submitted revision 963419
> JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-4774
> URL: https://issues.apache.org/jira/browse/AXIS2-4774
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> History:
> The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
> Problem:
> If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
> Solution:
> The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
> If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4774.
-----------------------------------
Resolution: Fixed
submitted revision 963419
> JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-4774
> URL: https://issues.apache.org/jira/browse/AXIS2-4774
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> History:
> The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
> Problem:
> If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
> Solution:
> The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
> If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4774.
-----------------------------------
Resolution: Fixed
submitted revision 963419
> JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-4774
> URL: https://issues.apache.org/jira/browse/AXIS2-4774
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> History:
> The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
> Problem:
> If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
> Solution:
> The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
> If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4774) JAX-WS: Wrong classloader may be used
to marshal data for a client JAX-WS applicatoin
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4774.
-----------------------------------
Resolution: Fixed
submitted revision 963419
> JAX-WS: Wrong classloader may be used to marshal data for a client JAX-WS applicatoin
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-4774
> URL: https://issues.apache.org/jira/browse/AXIS2-4774
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> History:
> The JAX-WS client runtime must build a JAXBContext to marshal the JAX-WS Web service data. The context ClassLoader on the thread is used to find the classes and build the JAXBContext.
> Problem:
> If the customer or other code changes the context ClassLoader, then the JAX-WS marshaling on the client may fail with a MarshalException.
> Solution:
> The JAXProxyHandler (which is the code that controls the client proxy construction) is changed to inspect the context ClassLoader and the ClassLoader of the SEI.
> If the class loaders are different, the runtime determines which one to use (prefering the one that loaded the SEI).
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org