Hi Lou, it's good to hear that you are still banging on Axis. Axis doesn't make it easy to morph the message elements while the message is in the processing pipeline. After the XML string has been converted to SOAP elements, the definition is locked down. For example, as you probably found, MessageElement.setObjectValue() will throw a fault if the textnode is already set.
It would be interesting to remove this protection (and in a few other places as well) and see if Axis still passes all functional tests. I'm interested in other committers explaining the rational for making the element read-only. I know that there is a bit of synchronization going on between the XMLString representing the message and the elements, but the current code based makes it extremely cumbersome to modify a message in the pipeline. /Chris http://cvs.apache.org/~haddadc -----Original Message----- From: lou fox [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 10:09 AM To: '[EMAIL PROTECTED]' Subject: Adding a text node to a MessageElement How do I change a textnode in a MessageElement? I know I can get the value of the textnode by calling the getValue() method, but how do I change it to something else? setObjectValue(), and addTextNode() didn't seem to work correctly. Does anyone know how to do this?
