axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Shahi (JIRA)" <>
Subject [jira] Commented: (AXIS-1469) Updates not effective after saveChanges() or writeTo()
Date Tue, 02 Nov 2004 15:23:33 GMT
     [ ]
Ashutosh Shahi commented on AXIS-1469:

   As I said earlier, the above problem occurs because each time saveChanges() is called on
soapEnvelope, the representation of soap envelope is changed to FORM_OPTIMIZED.
   So, to get over this issue, we can remove the statement at org.apache.axis.SOAPPart, line
487, from axis code:

setCurrentForm( array, FORM_OPTIMIZED );    

   This will solve the problem of saveChanges() not being effective on second call. As i see
it, we are converting to FORM_OPTIMIZED just to get a byte or binary representation of contents
for optimization, which anyway is being obtained when required. So, it should not affect any
other part of code. Can i go ahead and remove the above line from saveChanges() method to
solve the above problem? Any comments?

> Updates not effective after saveChanges() or writeTo()
> ------------------------------------------------------
>          Key: AXIS-1469
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: SAAJ
>     Versions: 1.2 Beta
>  Environment: JDK 1.4.2, Resin 2.1.14
>     Reporter: Mattias Jiderhamn
>     Priority: Critical

> Not sure how to explain this in an understandable manner, but run this code and you will
clearly see the problem:
>   SOAPMessage soapMessage = MessageFactory.newInstance().createMessage();
>   SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope(); // Get handle
to envelope
>   // soapMessage.writeTo(System.out); // This would give the same results
>   soapMessage.saveChanges(); // This converts the SOAP message to String form (as a Fix
for Bug 16418???)
>   soapEnvelope.addChildElement("foo", "bar", "http://foo/bar"); // Add child elements
>   soapMessage.writeTo(System.out); // The message is already in String form, and changes
have no effect

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message