Re: [Axis2] Changed OMNode

[Eran Chinthaka]

Yes, we wanted to make this immutable, so do namespaces.   Regards, Chinthaka ----- Original Message ----- From: Shahi, Ashutosh To: axis-dev@ws.apache.org Sent: Monday, May 23, 2005 8:46 PM Subject: RE: [Axis2] Changed OMNode OK, I have managed to overcome this issue by calling the get/set methods based on the NodeType. I think that should be the correct way as well. But I still have a question. There are no setter methods in OMText. We just have constructor and get methods. The way I am doing right now is calling the discard() method followed by calling a new constructor. But calling a set method directly for text will definitely be more efficient. Any reasons why a set method should be avoided here?   -Ashutosh From: Shahi, Ashutosh Sent: Monday, May 23, 2005 2:13 PM To: axis-dev@ws.apache.org Subject: [Axis2] Changed OMNode   Hi Eran,             The OMNode getValue() and setValue() methods have been removed in the new API. I had been using it extensively in the SAAJ implementation which has similar methods for Node class. How do you expect the get/set values now given a OMNode? I could not find any alternative from the existing methods.   -Ashutosh