You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/07/21 17:28:40 UTC

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

The following comment has been added to this issue:

     Author: Mattias Jiderhamn
    Created: Wed, 21 Jul 2004 8:27 AM
       Body:
This causes severe problems for us since a third party API that creates SOAP messages has the habit of calling saveChanges() every now and then.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1469?page=comments#action_36810

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1469

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
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Mattias Jiderhamn

    Created: Wed, 21 Jul 2004 8:24 AM
    Updated: Wed, 21 Jul 2004 8:27 AM
Environment: JDK 1.4.2, Resin 2.1.14

Description:
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



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Posted by Yves Langisch <li...@langisch.ch>.
Good point Mattias...Struggled many times over this issue. Had to use a 
workaround so far.

Yves

axis-dev@ws.apache.org wrote:

>The following comment has been added to this issue:
>
>     Author: Mattias Jiderhamn
>    Created: Wed, 21 Jul 2004 8:27 AM
>       Body:
>This causes severe problems for us since a third party API that creates SOAP messages has the habit of calling saveChanges() every now and then.
>---------------------------------------------------------------------
>View this comment:
>  http://issues.apache.org/jira/browse/AXIS-1469?page=comments#action_36810
>
>---------------------------------------------------------------------
>View the issue:
>  http://issues.apache.org/jira/browse/AXIS-1469
>
>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
> Components: 
>             Basic Architecture
>   Versions:
>             1.2 Beta
>
>   Assignee: 
>   Reporter: Mattias Jiderhamn
>
>    Created: Wed, 21 Jul 2004 8:24 AM
>    Updated: Wed, 21 Jul 2004 8:27 AM
>Environment: JDK 1.4.2, Resin 2.1.14
>
>Description:
>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
>
>
>
>---------------------------------------------------------------------
>JIRA INFORMATION:
>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
>
>If you want more information on JIRA, or have a bug to report see:
>   http://www.atlassian.com/software/jira
>
>  
>