Thanks for your remind. I will do that the next time.
And I still have a question on the exception handling. As you know, the
actural exception is wrapped in many wrapper exceptions. So the exception
process will have some problems to select the right exception handler.
Is the following the best practise for exception handling scenario:
try {
// sca method call
} catch (RMIException e) {
if (e.getCause().getCause() instanceof NotEnoughMoney) {
System.out.println("do not have enough money!");
} else {
System.out.println("other exception");
}
}
Or do we have any best practise for handling the wrapped application
exception?
Regards,
Yang Sun
2007/9/26, Jean-Sebastien Delfino <[EMAIL PROTECTED]>:
>
> Sun Yang wrote:
> > Hi, Raymond:
> >
> > Thanks for your confirmation. I will do that when I back to work
> tomorrow.
> >
> > Regards,
> > Yang Sun
> >
> >
> >
>
> If you want you can also submit a small patch in the JIRA, looks like
> it's just a matter of changing the SpringInvocationException(String msg)
> constructor to SpringInvocationException(Exception cause) and use that
> new constructor in a few places in SpringInvoker :)
>
> If you try that and it works for you it'll be easy to get that fix in.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
