You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "tomas darbois (JIRA)" <de...@tuscany.apache.org> on 2008/08/25 14:19:44 UTC

[jira] Commented: (TUSCANY-2545) Exception and RMI binding : propagating an exception.

    [ https://issues.apache.org/jira/browse/TUSCANY-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625334#action_12625334 ] 

tomas darbois commented on TUSCANY-2545:
----------------------------------------

Perhaps this is not an issue, in Tuscany point of view, can we have an update on the matter from one dev. 

There are workarounds for users, but the usual way to handle exception doesn't work. :) 

> Exception and RMI binding :  propagating an exception.
> ------------------------------------------------------
>
>                 Key: TUSCANY-2545
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2545
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Windows 2000; JDK 1.6_05 or JDK 1.5_015, Maven 2.0.9
>            Reporter: tomas darbois
>             Fix For: Java-SCA-Next
>
>         Attachments: calculator-exception.rar
>
>
> Let's say we have a Calculator.
> The client connects through SCA and binding RMI to the calculator. The calculator connects to the "divider"  through SCA and binding RMI.
> The divider raise a ZeroException (an exception that is declared as being thrown by divide method, exception known only by Calculator and Divider ) he found that he has the divisor = 0 and didn't try to do the computation and instead throws this exception.
> Calculator catches the exception and raise a new exception ServiceFatalException known by Client and Calculator (code = << throw new ServiceFatalException( "A string message", e); >>     where e is the ZeroException that has been caught).
> Client is trying to catch the exception ServiceFatalException.
> This architecture is failing because the RMI binding in client part tries to find the class "ZeroException" that is not defined in that environment. 
> In case we add in the classpath the class ZeroException, he successfully recovers a ServiceFatalException.
> I'm joining an example containing the 3 elements (the 2 standalone server and the client).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.