-memory services and we need to optimize for that.
We can document that application code should not return exceptions
as part of the message signature.
Jim
On Sep 8, 2006, at 5:14 PM, Raymond Feng wrote:
Hi,
I notice that we use the message body to flow business exceptions
back
:
Hi,
I notice that we use the message body to flow business exceptions
back to the client with the following code from TargetInvoker
implementations.
public Message invoke(Message msg) throws
InvocationRuntimeException {
try {
Object resp = invokeTarget(msg.getBody());
msg.setBody
PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Friday, September 08, 2006 11:39 PM
Subject: Re: Flow business exceptions back to the client
I don't think there is any valid application scenario for this even if it
is technically legal in Java. I would prefer we stick with our original
decision
8, 2006, at 5:14 PM, Raymond Feng wrote:
Hi,
I notice that we use the message body to flow business
exceptions back to the client with the following code from
TargetInvoker implementations.
public Message invoke(Message msg) throws
InvocationRuntimeException {
try {
Object resp
Hi,
I notice that we use the message body to flow business exceptions back to
the client with the following code from TargetInvoker implementations.
public Message invoke(Message msg) throws InvocationRuntimeException {
try {
Object resp = invokeTarget(msg.getBody());
msg.setBody(resp
, 2006, at 5:14 PM, Raymond Feng wrote:
Hi,
I notice that we use the message body to flow business exceptions
back to the client with the following code from TargetInvoker
implementations.
public Message invoke(Message msg) throws InvocationRuntimeException {
try {
Object resp
