Yes - when I read the docs for the ResourceExistsSelector it seemed to be exactly what I wanted (still must try and write a small sample, though).
Yet again, Cocoon "knows what I want" before I even get there! Thanks for the helpful pointers. >>> [EMAIL PROTECTED] 2005/09/08 12:24:15 PM >>> On 08.09.2005 11:44, Bart Molenkamp wrote: > I don't think that this selector will always work. Maybe for files, but > other sources (such as cocoon://) always return true on Source.exists(). Derek only wants to check for file existence, so that's no problem. He only wants to react with different sources like internal pipelines. ResourceExistsSelector or ResourceExistsActions are valid for this use case. Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
