Hey guys,

I'm trying to upgrade an application from Tuscany 1.3.2 to 1.4 RC4,
the application uses binding.jms and I've noticed a marked change in
behaviour for Exception handling - could someone tell me if this is
expected and if there is any means of getting a handle on the original
Exception?

Basically, the service throws a UserException with a message, but on
the client side I get the following Exception hierarchy:

org.osoa.sca.ServiceRuntimeException
   -> org.osoa.sca.ServiceRuntimeException
      -> java.lang.reflect.InvocationTargetException
         -> org.apache.tuscany.sca.interfacedef.util.FaultException

Where the FaultException contains the original message from the UserException.

Back in 1.3.2, for Exceptions the client would have a reconsituted
equivilant of the original Exception thrown.

Any guidance would be greatly appreciated,

Cheers,

Dave.

Reply via email to