Wow !! seems like I've missed lot of action. :). Sorry guys, I couldn't access my mails properly since 8th, due to some mail server problem.
Anyway, Venkat has answered me, without me saying anything ;). Coming back to the problem. Yes, I agree with you all that there are some problems in OM, which are not that serious, due to tweaking, as Ajith mentioned. These days we are "cleaning" OM. So give us sometime to come up with a good OM. Problems I see in the current impl 1. Current impl was not done, thinking of supporting the full infoset. We have tried to optimize for SOAP messages. So things like Document has been removed. 2. When supporting SwA, there can be attachments which are not clearly linked to the SOAP message. So we need a mechanism to hold those attachments outside the SOAP envelope. One option is to have these in the Document. 3. The builder hierarchy is not good. StAXOMBuilder, MTOMBuilder and StAXSOAPModelBuilder should be handled better than now. 4. Serialising code some issues. So worth reconsidering to re-write that. Those are some of the problems we have. Let us come up with a proposal soon, hopefully within this week. But unfortunately this *MAY* affect some of the implementations on top of OM. So bear with us a bit. Thanks and Regards, Eran Chinthaka > -----Original Message----- > From: Venkat Reddy [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 21, 2005 9:00 PM > To: [email protected] > Subject: Re: [Axis2] OMNodeImpl notes > > > > http://ws.apache.org/axis2/api/org/apache/axis/om/impl/llom/OMTextImpl.htm > l > > btw, it looks like OMTextImpl already has setFirstChild and > getFirstChild methods!! may be the remains of last refactoring? > > - venkat >
