Aleksander Slominski wrote: > content - it will require to keep per entity position since > beginning but it should be the only change and it should not > be difficult?
It *seems* easy but it's not. The only reliable way of doing this is to write custom readers for every conceivable character encoding so that you can keep track of byte vs. char location in the XML document stream. > positioning is the only misising feature that prevents me from > using Xerces2 for efficient SOAP pull parsing :-) I'm having trouble buying that conclusion. :) > instead of pinpointing i can pass my own reader that will keep > content of incoming input in a growable buffer. however i still Unless your reader only returns one char at a time, this is not going to work because the parser reads the input in chunks. Therefore, the location your reader reports will be past the actual point where the scanner is looking at markup. And even if your reader limited chunking calls to a single char at a time, this is grossly inefficient. If you're relying on this provide the performance you need, then I would suggest attacking the performance from another angle. > how difficult would it be to do? i would be happy to do it > (all actually looks not that complex) but i have no > experience with X2 codebase... You're welcome to try but I would not recommend it. And that has nothing to do with the Xerces2 codebase -- I'm speaking from years of experience in writing XML parsers. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
