Hi Sanjiva, We did try to turn off the tree building (caching) and the response just hung. This scenario is included in the JUnit test of the PTR. If you can just take a look at the junit and see if something's wrong with what we did, would really appreciate your advice on how to fix it on our side.
Lakshmi -----Original Message----- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 12, 2006 8:50 PM To: [email protected] Cc: [email protected]; Lakshmi Chaparala Subject: Re: [Axis2][Axiom]Always building Object Model .. no streaming atserver response flow Hi Srinath, We've dealt with this already .. Axiom does *not* always build the object model before sending .. what it does is pull and push. The writer is responsible for turning off the tree building (caching) if the message is not needed. In any case, have you seen the recent performance numbers? I'd say we're doing just fine. In your streaming scenario, is the XML you're trying to stream out in Axiom? If not you have to pay the price of axiom-izing (i.e., providing a stax reader). Sanjiva. On Wed, 2006-04-12 at 16:19 -0400, Srinath Perera wrote: > Hi Guys; > > According to http://issues.apache.org/jira/browse/AXIS2-483 it sound > like axiom always build the object model before sending out the > message. (e.g. If nobody accsess the body, we should write the object > diectly to output stream, no need to build the tree) > > If that is the case there will be huge overhead. > > Reporter of http://issues.apache.org/jira/browse/AXIS2-483 asked me > about it. I do not have time to work on it. I do wan't at least try to > help them. Can we call this a blocker for 1.0 release? It is a major > bug IMO > > thoughts? > Srinath > > -- > ============================ > Srinath Perera: > http://www.cs.indiana.edu/~hperera/ > http://www.bloglines.com/blog/hemapani
