Hi Michele:
As it explains in the JavaDoc, onMessage(msgContext) is called every
time a NON-FAULT message is received. So if you had a custom OUT-IN-IN
MEP, that method would usually be called twice. The onComplete() method
is *always* called at the end of an MEP, regardless of the outcome. So
for a standard OUT-IN MEP, you will get exactly one of [onMessage(),
onFault(), onError()] followed by onComplete().
If this wasn't made clear by the JavaDoc, let us know so we can attempt
to improve it.
Thanks,
--Glen
Michele Mazzucco wrote:
oops... the two methods are actually onMessage() and onComplete() [1]
Michele
[1] http://www.nabble.com/switch-from-Callback-AxisCallback-%
28with-problems%29-tf4118188.html
On Sun, 2007-07-22 at 21:45 -0400, Eran Chinthaka wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michele Mazzucco wrote:
Deepal,
when shall I use AxisCallback.onMessage() instead of
AxisCallback.onMessage(MessageContext msgContext)?
Do we have two methods? I can see only the latter now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGpAhAjON2uBzUhh8RAk1cAKCq26aS2LRlX+A0nzIzXg6oCJD+7gCfVTDd
Bl6NXMyMMXVpWjgGWbhQEW0=
=UTZs
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]