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 "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/04/10 05:00:06 UTC
[jira] Updated: (AXIS2-3722) Invalid SOAPMessage caching in
SoapMessageContext
[ https://issues.apache.org/jira/browse/AXIS2-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated AXIS2-3722:
-------------------------------
Attachment: AXIS2-3722.patch
Patch to SoapMessageContext to detect changes in the Message of the underlying MessageContext (and a test case).
> Invalid SOAPMessage caching in SoapMessageContext
> --------------------------------------------------
>
> Key: AXIS2-3722
> URL: https://issues.apache.org/jira/browse/AXIS2-3722
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 1.4, nightly
>
> Attachments: AXIS2-3722.patch
>
>
> SoapMessageContext.getMessage() will always return a cached copy of the SOAPMessage even though the underlying message in org.apache.axis2.jaxws.core.MessageContext was changed (i.e. using messageCtx.getMEPContext().setMessage()). The SoapMessageContext must not cache the SOAPMessage or it should detect when the underlying Message changes.
--
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