Is there a dedicated processor that raises exeptions in XPL?

> I was wondering if there is an existing processor or other mechanism defined
> that can be called from an XPL pipeline to explicitly raise/throw an
> exception?
>
> My rationale for needing this is that in an ideal world all XPL
> inputs/outputs would be as expected, but in some situations particular
> inputs/outputs can occur that you do not want to continue processing
> normally. Instead you would like to throw an exception which would be
> handled by the error pipeline (or a custom error pipeline).
>
> I had been thinking of creating a custom processor that takes an input
> describing the reason for the problem. This would then log the error and
> throw an OXFException which I believe should then be caught by the error
> pipeline.
>
> However before doing this, I thought I should check to see if this sort of
> functionality was already catered for by XPL? Alternatively, if anyone
> believes there is a better mechanism for dealing with this situation then
> please can you give me some pointers on how to handle this scenario.
>
> Thanks,
> Neil Crofts.
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

> Hi Neil,
>
> Yes, there an error processor:
>
> <p:processor name="oxf:error">
>     <p:input name="config">
>         <config>My error message</config>
>     </p:input>
> </p:processor>
>
> Alex
>
> On 10/19/06, Neil Crofts (Gmail) <[hidden email]> wrote:
> > I was wondering if there is an existing processor or other mechanism defined
> > that can be called from an XPL pipeline to explicitly raise/throw an
> > exception?
> >
> > My rationale for needing this is that in an ideal world all XPL
> > inputs/outputs would be as expected, but in some situations particular
> > inputs/outputs can occur that you do not want to continue processing
> > normally. Instead you would like to throw an exception which would be
> > handled by the error pipeline (or a custom error pipeline).
> >
> > I had been thinking of creating a custom processor that takes an input
> > describing the reason for the problem. This would then log the error and
> > throw an OXFException which I believe should then be caught by the error
> > pipeline.
> >
> > However before doing this, I thought I should check to see if this sort of
> > functionality was already catered for by XPL? Alternatively, if anyone
> > believes there is a better mechanism for dealing with this situation then
> > please can you give me some pointers on how to handle this scenario.
> >
> > Thanks,
> > Neil Crofts.
> >
> >
> >
> >
> >
> >
> > --
> > You receive this message as a subscriber of the [hidden email] mailing list.
> > To unsubscribe: mailto:[hidden email]
> > For general help: mailto:[hidden email]?subject=help
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
> >
>
>
> --
> Blog (XML, Web apps, Open Source):
> http://www.orbeon.com/blog/
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>