cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: unroll behavior in the ExceptionSelector
Date Thu, 10 Apr 2003 13:05:08 GMT
juergen.seitz@basf-it-services.com wrote:

>Hi Sylvain,
>
>sorry, we didn´t noticed that you use recursion to unroll.
>Of course, your solution fits our needs.
>
>We only propose one improvement :-)
>
>
>      if (cause != null) {
>            String name = findName(cause);
>            if (name != null){
>                  return name;
>            }
>      }
>
>The result would be, that if you have a cause, that is not configured,
>you don´t return null, but the name of the cause's parent, that is
>configured.
>(Sounds a little bit confusing (-: )
>

No, no : that's a good idea, that I will put in right away ! This means 
you unroll the exception chain up to the last exception that has a name 
and shoudn't be unrollable.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



Mime
View raw message