SOAP attachment serialized badly when logging is turned on
----------------------------------------------------------
Key: AXIS-2608
URL: https://issues.apache.org/jira/browse/AXIS-2608
Project: Apache Axis
Issue Type: Bug
Components: Serialization/Deserialization
Affects Versions: 1.4
Environment: java full version "1.5.0_09-b03"
Reporter: Julian Morrison
When generating SOAP request with an attachment, normally, the attachment is
referred to with an ID and included after prefixed with its ID. In this bug, a
blank attachment is included after, referenced with the proper ID, and the
actual attachment follows, with some other random ID referenced from nowhere.
This was happening when log4j.xml was available, and not when it wasn't. The
cause appears to be that repeated XML serialization of the SOAP request message
only works properly the first time. There's a conditional logging block in
src/org/apache/axis/client/Call.java line 2752 which serializes the message to
log it, and then it's subsequently re-serialized to send it. If logging is
unavailable, the block is skipped, it only gets serialized once, and is sent
correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
