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

David Blevins commented on AXIS-1469:
-------------------------------------

I ran into this same failure on the OpenEJB/Axis integration.  This failure has 
nothing to do with form optimization, but rather that the recorded state in the 
SAX2EventRecorder is preferred to the state in the MessageElement instance even 
after they have once been marked dirty.

I've submitted two fixes for these issues:
  AXIS-2069
  "SAX2EventRecorder.replay called even after message is validly marked dirty"
  http://issues.apache.org/jira/browse/AXIS-2069

And a small related fix where things weren't marked dirty:
  AXIS-2068
  "Missing setDirty flags in SAAJ tree modification (detachNode and setParent)"
  http://issues.apache.org/jira/browse/AXIS-2068



> Updates not effective after saveChanges() or writeTo()
> ------------------------------------------------------
>
>          Key: AXIS-1469
>          URL: http://issues.apache.org/jira/browse/AXIS-1469
>      Project: Apache 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

Reply via email to