[AXIS-283] AXIS does not serialize attributes placed at the body element

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: beta-3
• Component/s: Serialization/Deserialization
• Environment: Operating System: Windows NT/2K; Platform: PC
• Bugzilla Id: 11982
• Assignee: Unassigned
• Reporter: Mario Jeckle
• Created: 23/Aug/02 23:29
• Updated: 16/Feb/11 13:21
• Resolved: 24/Feb/04 00:18

Description

Hi,

We tried recently to incorporate Digital Signatures according the W3C's note
(http://www.w3.org/TR/2001/NOTE-SOAP-dsig-20010206/) into Axis v1 beta 3.

The cited note requires the presence of an XML attribute within the element
SOAP-Body.

Although, it is perfectly doable to add an XML attribute to the SOAP-Body
element this attribute never is serialized down to the XML stream sent over the
wire, even if it is correctly placed within the internal SOAPBody data structure.

After some time of investigating we discovered that the method
"outputImpl(SerializationContext context)" which is implemented in
org.apache.axis.message.SOAPBody statically serializes SOAP's body element using
the call
"context.startElement(new QName(soapConstants.getEnvelopeURI(),
Constants.ELEM_BODY), null);"

Obviously, this call ignores attributes eventually existing within the memory
structures.

To circumvent the problem of loosing attributes eventually added to the SOAP
body simply changing the "null" into a "this.getAttributes()" would certainly do
the job.

Best Regards,
Mario
–
Mario Jeckle
DaimlerChrysler Research and Technology
Research Information and Communication/Data and Process Management

MailTo:[e-mail]

Forthcoming: International Workshop on Web Services in Research,
Standardization, and Deployment (WS-RSD'02)
http://www.jeckle.de/ws-rsd

URL: http://www.jeckle.de
PGP public key: http://www.jeckle.de/marioJeckle.pub