[ http://issues.apache.org/jira/browse/AXIS-1469?page=comments#action_12313358 ]
Mattias Jiderhamn commented on AXIS-1469: ----------------------------------------- As you can see this issue was reported almost a year ago. I was assigned to spend some time looking at Hermes; usage, dependencies and compatibility. A number of issues arose, and this is one of them. After my investigation it seems we may never actually use Hermes (I personally hope we never will, partially because of compatibility issues like this). I just thought I would be kind enought to report what appeared to me like an obvious bug. I had the impression that SAAJ API implementations would be just as interchangeable as XML parsers. You should be able to just replace one JAR with another. I don't know of any requirement to call saveRequired() before saveChanges(), and Hermes does fine without it using the SAAJ reference implementation packed with it. So from my very ignorant point of view, Axis seems to be incorrect. But, to be completely honest, I - don't have the time to actually investigate this any futher (unless we eventually decide to use Hermes) - am unfamiliar with the concept of JAX-RPC Handlers (although from the example given, it seems to be something that need to be changed in Hermes, and not something I can do in my code; especially in the ebMS "server part" web application that contains no or little additional code, but is invoked solely by SOAP calls) - have not looked at Hermes during the last 10 months, so this *may* already have been resolved - don't REALLY care If you claim Axis is right and Hermes is wrong, I guess I have to take your word for it. If we end up actually using Hermes, I will file a bug report over there or see if I can create some Axis specific work-around. > 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
