You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2009/02/25 14:07:02 UTC

[jira] Commented: (TUSCANY-2867) Checked Exceptions are thrown as ServiceRuntimeExceptions over non-default wireformats

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

Simon Laws commented on TUSCANY-2867:
-------------------------------------

You don't now rely on the boolean fault flag in the message when extracting faults from Object type messages. However the ObjectMessageProcessor doesn't override the createFaultMessage operation so the flag is still added to Object type messages. Is that OK for you?

Simon

> Checked Exceptions are thrown as ServiceRuntimeExceptions over non-default wireformats
> --------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2867
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2867
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA JMS Binding Extension
>            Reporter: Kaushik Mukherjee
>            Assignee: Simon Laws
>         Attachments: TUSCANY-2867.patch
>
>
> All exceptions are thrown as ServiceRuntimeExceptions over the non-default wireformats. We've added a patch that returns an InvocationTargetException for all checked exceptions in AbstractMessageProcessor. For the object wireformat, we felt that we should not require a boolean property in order to handle exceptions and overrode this behavior in the ObjectMessageProcessor. For the other wireformats it seemed reasonable to check for the property so we did not have to check for an instanceof ObjectMessage on every call. 

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