Joerg Heinicke wrote:
When it is sendPage(): Is it correct that the pipeline 'content/' ...
works on that file? Then it's maybe a sync problem, the write to disk
might not have been finished. Another reason might be the chunking of
output if the content-length header is set to a wrong size. Can you see
the value of the header on client side?
If i look at PageInfo in firebird it says it's unknown.
The error message is obvious IMO.
Sorry, a case of not enough coffee.. ;) However, the code is now failing
on pipelineUtil.processToDOM() reporting: Streaming of an internal
pipeline is not possible with a reader. Changing the pipeline to
internal-only="false" doesn't solve the problem.
groetjes, su.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
