Ignacio,
I think the updated code implements the behavior described in the
assembly spec. There was another thread related to callbacks where Dave
Booz helped to clarify some of the use cases.
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg12874.html
I think this update may also resolve TUSCANY-1052.
Ignacio Silva-Lepe wrote:
Hi Jim,
I am not sure I follow the modification to ConnectorImpl. You remove
the check for operationHasCallback altogether in the forward direction
and add a check for isOneWayOperation in the callback direction.
As far I understand, Operation.isNonBlocking (which determines the
value of isOneWayOperation) is only true when there is a @OneWay
annotation.
Are we supposed to use @OneWay explicitly to make forward and
callback methods non-blocking now? It seems to me to be the only
way in which ConnectorImpl can produce the right outcome as it
currently stands. If so, is the spec going to change to require the
use of @OneWay for this purpose?
At the moment, both the simplecallback and the inner.composite
samples do not work properly.
--
Matthew Sykes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
