Thorsten Scherler wrote:
El mar, 29-11-2005 a las 10:04 +0000, Ross Gardler escribió:
David Crossley wrote:
...
My intention was to see the code and then try and make a suggestion as
to how we can avoid this bottleneck. I'm guessing there is a good
technical reason for needing a DOM.
Hmm, actually yes. Do you remember the @xpath injection? How can you do
this via sax events. ATM I am generating the response in DOM to inject
all the xpath stuff (which is harder that I thought) coming from the
contracts.
Perhaps Thorsten could let us know more about this problem and see what
we can come up with as a community.
Eager to hear what u think how we can have the xpath injection with SAX.
The problem I have is since I added the injection stuff it is not
working anymore like I expected, so I am not keen to check something in
that is not working ATM.
Short of writing a custom include processing within the SAX processing I
can't think of anything. Unless this would be easier than solving your
current problem I'd think this is one for a future enhancement.
Ross
