Re: cocoon:/ does not work with SourceResolver (was: Re: Flow's processePipelineTo inside a Transformer?)

2003-11-27 Thread Bruno Dumon
On Wed, 2003-11-26 at 21:32, Sebastian Klamar wrote: > * Bruno Dumon [2003-11-26 14:29 +0100] wrote: > > On Wed, 2003-11-26 at 14:04, Sebastian Klamar wrote: > > > But for cocoon:/ and cocoon:// prefixed URLs (like > > > »cocoon://samples/«) I get no response. The response has always > > > mime ty

Re: cocoon:/ does not work with SourceResolver (was: Re: Flow's processePipelineTo inside a Transformer?)

2003-11-26 Thread Sebastian Klamar
* Bruno Dumon [2003-11-26 14:29 +0100] wrote: > On Wed, 2003-11-26 at 14:04, Sebastian Klamar wrote: > > But for cocoon:/ and cocoon:// prefixed URLs (like > > »cocoon://samples/«) I get no response. The response has always > > mime type text/xml and content length -1. > > Can you do source.getInp

Re: cocoon:/ does not work with SourceResolver (was: Re: Flow's processePipelineTo inside a Transformer?)

2003-11-26 Thread Bruno Dumon
On Wed, 2003-11-26 at 14:04, Sebastian Klamar wrote: > Bruno, > > thank you for your reply. > > * Bruno Dumon [2003-11-25 19:28 +0100] wrote: > > If you're writing a custom transformer, you can use the SourceResolver > > to resolve a cocoon: URL, which is similar to the processPipelineTo in > > f

cocoon:/ does not work with SourceResolver (was: Re: Flow's processePipelineTo inside a Transformer?)

2003-11-26 Thread Sebastian Klamar
Bruno, thank you for your reply. * Bruno Dumon [2003-11-25 19:28 +0100] wrote: > If you're writing a custom transformer, you can use the SourceResolver > to resolve a cocoon: URL, which is similar to the processPipelineTo in > flowscript. I've tried this. But for cocoon:/ and cocoon:// prefixed