[jira] Commented: (AXIS-1469) Updates not effective after saveChanges() or writeTo()

["Mattias Jiderhamn (JIRA)" <ax...@ws.apache.org>]

    [ http://issues.apache.org/jira/browse/AXIS-1469?page=comments#action_12313241 ] 

Mattias Jiderhamn commented on AXIS-1469:
-----------------------------------------

So, what your're really saying is: if I want to use a third party API that calls the standard SOAP API as of my inital example code (in our case Hermes ebXML Message Services), I *MUST NOT* use Apache Axis as SOAP implementation.
Right?

(Surely I'm no expert on the subject, but I find it hard to believe this would be a correct implementation of the SOAP API spec.)

> Updates not effective after saveChanges() or writeTo()
> ------------------------------------------------------
>
>          Key: AXIS-1469
>          URL: http://issues.apache.org/jira/browse/AXIS-1469
>      Project: Axis
>         Type: Bug
>   Components: SAAJ
>     Versions: 1.2 Beta
>  Environment: JDK 1.4.2, Resin 2.1.14
>     Reporter: Mattias Jiderhamn
>     Assignee: Venkat Reddy
>     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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira