[
https://issues.apache.org/jira/browse/TUSCANY-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467148
]
Rick Rineholt commented on TUSCANY-1034:
----------------------------------------
I've produce a new iTest subdirectory
http://svn.apache.org/repos/asf/incubator/tuscany/java/testing/sca/itest/exceptionTests
The first test is intra-composite pojo component to pojo component. It
checks both checked and unchecked exceptions. This seems work, the source
component is capturing the exact application defined exceptions as expected.
Not 100% sure how to reproduce this in a local scenario.
The other wiring across bindings (web services) I'm not sure how to ser/des
exceptions so the are accurately produced by the same class. Would need to
look how SDO, JAXB, etc address (support) this. How would this work for C++,
PHP? They should be able to reproduce the exception too. (i.e. this shouldn't
be a Java only solution.)
> Need to add support for business exceptions - at least in simple
> intra-Composite case to begin with
> ---------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1034
> URL: https://issues.apache.org/jira/browse/TUSCANY-1034
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core
> Affects Versions: Java-SCA-M3
> Environment: M2- level code
> Reporter: Scott Kurz
> Assigned To: Rick Rineholt
> Fix For: Java-SCA-M3
>
>
> Not sure how to track this one. It's possible adding support for business
> exceptions is an effort which spans a bunch of different parts.
> To start with, as the comment acknowledges the DataBindingInteceptor (sic)
> needs to do something other than the current:
> // FIXME: How to deal with faults?
> if (resultMsg.isFault()) {
> // We need to figure out what fault type it is and then transform
> it back the source fault type
> throw new InvocationRuntimeException((Throwable) result);
> }
> If no transform was needed this code would have been fine simply doing:
> return resultMsg;
> If this would not be worked on more completely it might be worth enabling
> this simple case for the time being.
> Later, probably in another JIRA, code such as the Axis2 binding might need to
> be tweaked to handle business exceptions/faults. (For example we might
> unwrap an AxisFault). Depends on how this is
> handled.
> In the meantime I wanted to get this down as a TODO.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
