Glen,
it was clear.
What is now more difficult to achieve, instead, is to handle multiple
MEPs using the same callback since the onComplete() is called n times
(where n is the number of expected responses), while it would be much
better if it was called only once.
Michele
On Mon, 2007-07-23
Erik,
You are absolutely right!!! we are missing
axis2-ant-plugin-SNAPSHOT.jar from the bin dist. the name changed
after we moved to maven2 based build. I will update the build by
tonight hopefully.
thanks,
dims
On 7/23/07, Erik Bertelsen [EMAIL PROTECTED] wrote:
2007/7/20, Deepal Jayasinghe
2007/7/24, Davanum Srinivas [EMAIL PROTECTED]:
Erik,
You are absolutely right!!! we are missing
axis2-ant-plugin-SNAPSHOT.jar from the bin dist. the name changed
after we moved to maven2 based build. I will update the build by
tonight hopefully.
Thanks alot :-)
I actually tried to build
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
2007/7/20, Deepal Jayasinghe [EMAIL PROTECTED]:
Hi all,
I have upload Axis2 1.3 RC2 artifact into my apache home location [1] ,
.
[1] : http://people.apache.org/~deepal/axis2/1.3-RC2/
...
Thanks
Deepal
I feel at little stupid about asking this, but I just cannot find the
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.
-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
Hi all,
I have upload Axis2 1.3 RC2 artifact into my apache home location [1] ,
please test and make sure all the JIRAs we marked as fixed are there in
the release , in addition to that if you find any issues with the
release please create a JIRA [2] , then we can fix that for next RC.
This
Deepal,
from the wiki I see that the async msg. receiver spawns a new thread if
the DO_ASYNC property is set. Isn't it possible to use NIO (if my memory
is right Synapse already uses it and there were plans to port it to
Axis2 as well)?
Thanks,
Michele
On Fri, 2007-07-20 at 18:04 +0530,
Hi Michele ,
Please create a JIRA then let's see what the community think about that
. If everyone is ok then lets do that changes.
FYI: We have already integrated NIO stuff in to Axis2
Thanks
Deepal
Deepal,
from the wiki I see that the async msg. receiver spawns a new thread if
the
Done. https://issues.apache.org/jira/browse/AXIS2-2993
Michele
On Fri, 2007-07-20 at 18:33 +0530, Deepal Jayasinghe wrote:
Hi Michele ,
Please create a JIRA then let's see what the community think about that
. If everyone is ok then lets do that changes.
FYI: We have already integrated NIO
Deepal,
when shall I use AxisCallback.onMessage() instead of
AxisCallback.onMessage(MessageContext msgContext)?
Thanks,
Michele
On Fri, 2007-07-20 at 18:04 +0530, Deepal Jayasinghe wrote:
Hi all,
I have upload Axis2 1.3 RC2 artifact into my apache home location [1] ,
please test and make
Add a repo that points to
http://people.apache.org/~deepal/axis2/1.3-RC2/m2-repo/
and use
groupIdorg.apache.axis2/groupId
version1.3-RC2/version
Thanks,
dims
On 7/20/07, Gertjan van Oosten [EMAIL PROTECTED] wrote:
As quoted from Deepal Jayasinghe [EMAIL PROTECTED]:
I have upload Axis2 1.3
13 matches
Mail list logo
