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 "Brian McDonald (JIRA)" <ax...@ws.apache.org> on 2007/02/15 23:20:05 UTC
[jira] Created: (AXIS-2629) Duplicate Attachements while in debug
mode
Duplicate Attachements while in debug mode
------------------------------------------
Key: AXIS-2629
URL: https://issues.apache.org/jira/browse/AXIS-2629
Project: Axis
Issue Type: Bug
Components: Serialization/Deserialization
Affects Versions: 1.4
Reporter: Brian McDonald
Here are the mainling list links to the original bugs reported against axis 1.1:
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200305.mbox/%3C20030516083732.26574.qmail@nagoya.betaversion.org%3E
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200306.mbox/%3C20030628202237.2036.qmail@nagoya.betaversion.org%3E
This was the proposed solution:
http://marc.theaimsgroup.com/?l=axis-dev&m=105673824931414&w=2
This solution does not work (at least not any longer) because the hash used to determine uniquenes of attachments is the hasCode on the DataHandler object (AttachmentsImpl.createAttachmentPart). A new DataHandler object is created each time seralize is called, so the DataHandler object will always be unique.
You need to check that the value object passed into the seralizer (which in turn is passed into the Source subclass which is passed into the DataHandler constructor is unique. This is difficult to do at the moment because the original value object usually isn't stored in the Source object, but rather it's resulting bytes are stored.
--
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