Carsten Ziegeler wrote:
> Torsten Curdt wrote:
>
>>
>>While using the XMLByteStreamCompiler and XMLByteStreamInterpreter
>>I found that the Compiler will store all SAXevent just fine. No matter
>>if it's a valid DocumentFragment of just a fragment of a X
Torsten Curdt wrote:
>
>
> While using the XMLByteStreamCompiler and XMLByteStreamInterpreter
> I found that the Compiler will store all SAXevent just fine. No matter
> if it's a valid DocumentFragment of just a fragment of a XML stream.
>
> But the interpreter assu
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
>
> While using the XMLByteStreamCompiler and XMLByteStreamInterpreter
> I found that the Compiler will store all SAXevent just fine. No matter
> if it's a valid DocumentFragment of just a fragment of a XML stream.
>
> B
While using the XMLByteStreamCompiler and XMLByteStreamInterpreter
I found that the Compiler will store all SAXevent just fine. No matter
if it's a valid DocumentFragment of just a fragment of a XML stream.
But the interpreter assumes that there is always a enclosing
startDocument/endDoc
Klaasen Tom wrote:
> Hi all,
>
> I had some troubles with the XMLByteStreamInterpreter today. I noticed it
> has recently changed (this morning), but I don't see how this change could
> cause the bug (but then again, I didn't examine it too closely ;) ).
>
>
n.de mailto: [EMAIL PROTECTED]
> Tom Klaasen wrote:
>
>
> Hi all,
>
> I had some troubles with the XMLByteStreamInterpreter today. I noticed it
> has recently changed (this morning), but I don't see
Hi all,
I had some troubles with the XMLByteStreamInterpreter today. I noticed it
has recently changed (this morning), but I don't see how this change could
cause the bug (but then again, I didn't examine it too closely ;) ).
At intermittent times, I got an ArrayIndexOutOfBound
