Exception Catcher doesn't always catch exceptions

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Exception Catcher doesn't always catch exceptions

Ryan Puddephatt
All,
    I had the following and it threw an exception because of no /result/message element exists, producing an invalid document

            <p:processor name="oxf:exception-catcher">
                <p:input name="data" href="#emailQueueQuery#xpointer(/result/message)"/>
                <p:output name="data" id="emailQueue" debug="EQ"/>
            </p:processor>

but the following catches the exception

            <p:processor name="oxf:identity">
                <p:input name="data" href="#emailQueueQuery#xpointer(/result/message)"/>
                <p:output name="data" id="emailQueueEx" debug="EQ"/>
            </p:processor>
           
            <p:processor name="oxf:exception-catcher">
                <p:input name="data" href="#emailQueueEx"/>
                <p:output name="data" id="emailQueue" debug="EQ"/>
            </p:processor>

why is the extra processor needed? Shouldn't it work with the first example?

Ryan
--

Ryan Puddephatt
Software Engineer
 
Teleflex Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotland
EH54 7DP
 
e> [hidden email]
t> +44(0)1506 407 110
f> +44(0)1506 407 108
w> www.teleflex.com

"Measuring programming progress by lines of code is like measuring aircraft building progress by weight." - Bill Gates
"If you lie to the compiler, it will get its revenge." - Henry Spencer
"It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free." - Steve McConnell
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." - Gerald Weinberg



--
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
Reply | Threaded
Open this post in threaded view
|

Re: Exception Catcher doesn't always catch exceptions

Alessandro Vernet
Administrator
Hi Ryan,

I would think that the first case should also catch the exception.
Would you have a simple pipeline we can use to reproduce this?

Now on the usefulness of this code, I am wondering what exactly you
are trying to do with this. Would you like to catch the case where
where is no /result/message? Why not use a p:choose/p:when to do this?

Alex

On 4/14/07, Ryan Puddephatt <[hidden email]> wrote:

>
>  All,
>      I had the following and it threw an exception because of no
> /result/message element exists, producing an invalid document
>
>              <p:processor name="oxf:exception-catcher">
>                  <p:input name="data"
> href="#emailQueueQuery#xpointer(/result/message)"/>
>                  <p:output name="data" id="emailQueue" debug="EQ"/>
>              </p:processor>
>
>  but the following catches the exception
>
>              <p:processor name="oxf:identity">
>                  <p:input name="data"
> href="#emailQueueQuery#xpointer(/result/message)"/>
>                  <p:output name="data" id="emailQueueEx" debug="EQ"/>
>              </p:processor>
>
>              <p:processor name="oxf:exception-catcher">
>                  <p:input name="data" href="#emailQueueEx"/>
>                  <p:output name="data" id="emailQueue" debug="EQ"/>
>              </p:processor>
>
>  why is the extra processor needed? Shouldn't it work with the first
> example?
>
>  Ryan
>
> --
>
>
>
>  Ryan Puddephatt
>  Software Engineer
>
>  Teleflex Group - IT UK
>  1 Michaelson Square
>  Livingston
>  West Lothian
>  Scotland
>  EH54 7DP
>
>  e> [hidden email]
>  t> +44(0)1506 407 110
>  f> +44(0)1506 407 108
>  w> www.teleflex.com
>
>  "Measuring programming progress by lines of code is like measuring aircraft
> building progress by weight." - Bill Gates
>  "If you lie to the compiler, it will get its revenge." - Henry Spencer
>  "It's hard enough to find an error in your code when you're looking for it;
> it's even harder when you've assumed your code is error-free." - Steve
> McConnell
>  "If builders built buildings the way programmers wrote programs, then the
> first woodpecker that came along would destroy civilization." - Gerald
> Weinberg
>
> --
> 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
>
>

--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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