axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1469) Updates not effective after saveChanges() or writeTo()
Date Fri, 01 Oct 2004 07:12:42 GMT
The following comment has been added to this issue:

     Author: Mattias Jiderhamn
    Created: Fri, 1 Oct 2004 12:11 AM
As I said, the problem arises in a third party API, which is supposed to be SOAP implementation
independent. So your workaround will not be of any help to me.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1469
    Summary: Updates not effective after saveChanges() or writeTo()
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis
             Basic Architecture
             1.2 Beta

   Reporter: Mattias Jiderhamn

    Created: Wed, 21 Jul 2004 8:24 AM
    Updated: Fri, 1 Oct 2004 12:11 AM
Environment: JDK 1.4.2, Resin 2.1.14

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