[ http://issues.apache.org/jira/browse/AXIS-1469?page=comments#action_62567 ] Guillaume Sauthier commented on AXIS-1469: ------------------------------------------
So, if you don't want a workaround, please use JAX-RPC Handler. Moreover, JAXRPC Handler are "standard" handlers and can be used in any JAXRPC Runtime, this is the more implementation independent solution, as it is even independent of Axis. The problem is that SOAPPart (the class used for form change) is a critical part in Axis, if we turn off the optimization all the time, performance will be very (very) bad. > 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 > 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
