On Aug 29, 2006, at 7:39 AM, Askild Aaberg Olsen wrote:
My experience is that if the referenced pipeline fails, Saxon reports
this as "unkown protocol cocoon", or something similar.
That is exactly right.
Try invoking the pipeline directly from your browser (if the pipeline
is not "internal-only"), then you should be able to view the error
dump.
Similarly for the "context:/" protocol... if no file exists at the
referenced path, you will see the "unknown protocol" error.
I guess this is really a bug in Saxon.
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
