Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1776310825.1118418708016.JavaMail.jira@ajax.apache.org>
Date: Fri, 10 Jun 2005 17:51:48 +0200 (CEST)
From: "Davanum Srinivas (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS-1469) Updates not effective after
 saveChanges() or writeTo()
In-Reply-To: <1901236581.1090423599971.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Davanum Srinivas commented on AXIS-1469:
----------------------------------------

I just checked the ebxmlms sources....they don't even check saveRequired() before calling saveChanges()...Did you open a bug with them?

thanks,
dims

> 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