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 "David Blevins (JIRA)" <ax...@ws.apache.org> on 2005/06/21 00:04:19 UTC
[jira] Created: (AXIS-2069) SAX2EventRecorder.replay called even after message is validly marked dirty
SAX2EventRecorder.replay called even after message is validly marked dirty
--------------------------------------------------------------------------
Key: AXIS-2069
URL: http://issues.apache.org/jira/browse/AXIS-2069
Project: Apache Axis
Type: Bug
Components: SAAJ
Versions: 1.2.1
Reporter: David Blevins
Attachments: recorder_replay.patch
SAX2EventRecorder.replay called even after message is validly marked dirty resulting in failures in writeTo and saveChanges. The result is that it is still considered "good" and all changes to the MessageElements are ignored. Not only should the MessageElements be the source of "truth" after the message is fully read then modified, but there is no point in keeping a record of the entire original message.
This patch detects when the message is fully read then checks on every setDirty to see if the recorder state is still relevant, if not it clears it out and nulls it so no further writeTo or saveChanges calls will not result in a replay of old state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-2069) SAX2EventRecorder.replay called even after message is validly marked dirty
Posted by "David Blevins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2069?page=all ]
David Blevins updated AXIS-2069:
--------------------------------
Attachment: recorder_replay.patch
> SAX2EventRecorder.replay called even after message is validly marked dirty
> --------------------------------------------------------------------------
>
> Key: AXIS-2069
> URL: http://issues.apache.org/jira/browse/AXIS-2069
> Project: Apache Axis
> Type: Bug
> Components: SAAJ
> Versions: 1.2.1
> Reporter: David Blevins
> Attachments: recorder_replay.patch
>
> SAX2EventRecorder.replay called even after message is validly marked dirty resulting in failures in writeTo and saveChanges. The result is that it is still considered "good" and all changes to the MessageElements are ignored. Not only should the MessageElements be the source of "truth" after the message is fully read then modified, but there is no point in keeping a record of the entire original message.
> This patch detects when the message is fully read then checks on every setDirty to see if the recorder state is still relevant, if not it clears it out and nulls it so no further writeTo or saveChanges calls will not result in a replay of old state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS-2069) SAX2EventRecorder.replay called even after message is validly marked dirty
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2069?page=all ]
Davanum Srinivas resolved AXIS-2069:
------------------------------------
Resolution: Fixed
Applied Patch.
> SAX2EventRecorder.replay called even after message is validly marked dirty
> --------------------------------------------------------------------------
>
> Key: AXIS-2069
> URL: http://issues.apache.org/jira/browse/AXIS-2069
> Project: Apache Axis
> Type: Bug
> Components: SAAJ
> Versions: 1.2.1
> Reporter: David Blevins
> Attachments: recorder_replay.patch
>
> SAX2EventRecorder.replay called even after message is validly marked dirty resulting in failures in writeTo and saveChanges. The result is that it is still considered "good" and all changes to the MessageElements are ignored. Not only should the MessageElements be the source of "truth" after the message is fully read then modified, but there is no point in keeping a record of the entire original message.
> This patch detects when the message is fully read then checks on every setDirty to see if the recorder state is still relevant, if not it clears it out and nulls it so no further writeTo or saveChanges calls will not result in a replay of old state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira