Hi,
I am currently working on a creating custom conduit that asynchronously
receives messages.
In the current implementation of Client &
org.apache.cxf.endpoint.ClientImpl - consumers of a conduit the
assumption
seems to be that invoke() is a synchronous operation as the javadoc
clearly states
/**
* Invokes an operation syncronously
* @param oi The operation to be invoked
* @param params The params that matches the parts of the input
message of the operation
* @param context Optional (can be null) contextual information for
the invocation
* @return The return values that matche the parts of the output
message of the operation
*/
Object[] invoke(BindingOperationInfo oi,
Object[] params,
Map<String, Object> context) throws Exception;
In a asynchronous transport like the one I am trying to adapt a Conduit
to, where I get the error/disconnect notifies asynchronous on a
different thread, how would I handle an exception condition?
Wanted to know if there are current workarounds/alternates to
ClientImpl/Client that support asynchronous message receives/exceptions
and plans, if any, to build one.
I am currently using CXF 2.1.1.
Thanks,
Ram
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
