On 27.05.2004 12:38, Suzan Foster 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.
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.The error message is obvious IMO.
That's exactly what I feared when I talking about wrong content-length: a reader is involved. I had a similar problem last week: http://marc.theaimsgroup.com/?t=108491743200003&r=1&w=4. A reader sets the content-length header. In general readers are prevented from being used in internal requests.
This has nothing todo with "internal-only" directly. "internal-only" determines whether a pipeline can be accessed from external or not.
You have an internal request for example when using cocoon:/ or when accessing a pipeline by using processPipeline (for both the old way and the new way using PipelineUtil). The question is only if it is recognized as internal request.
If you want to use processPipelineToDOM I guess you have XML. So instead of the reader you can use the file generator and a XML serializer.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
