Maybe you're using a file://... source in one of the generator/transformer components behind the pipeline?
And maybe a little bit off-topic, but from a CRON job (CRON thread), the cocoon:// source resolving is extremely slow and causes OutOfMemory errors (in my use-case, I used the cocoon:/ source for generating personal mails for each individual user in our system). Bart. > -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Monday, March 21, 2005 4:04 PM > To: [email protected] > Subject: Re: cocoon:// protocol and map:mount > > Gianugo Rabellino wrote: > > > > Actually no, I used cocoon:/. However, changing it with cocoon:// > > causes a SourceNotFoundException, with Cocoon seemingly using a > > file:// URL to resolve the inputstream, which is even weirder... does > > it rely on SourceResolver at all? > > > Yes, it does :( - hmm, so this is really a bug. Can you file it to > bugzilla, so it doesn't get lost? > > Carsten > > -- > Carsten Ziegeler - Open Source Group, S&N AG > http://www.s-und-n.de > http://www.osoco.org/weblogs/rael/
