That's excellent. However, for some reason I am not able to verify. I did a
full update and build, and when I run the async client I get the following,
which I don't think is what you mean by "null response" right?
Running helloworld.HelloWorldWSAsyncClientTestCase
log4j:WARN No appenders could be found for logger
(org.apache.axiom.om.util.StAX
Utils).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "Axis2 Task"
org.apache.tuscany.spi.wire.InvocationRuntimeEx
ception: org.apache.axis2.AxisFault: Incoming message input stream is null
at
org.apache.tuscany.binding.axis2.Axis2ReferenceCallback.onError(Axis2
ReferenceCallback.java:50)
at
org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvo
cationWorker.run(OutInAxisOperation.java:454)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
ker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
ker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.AxisFault: Incoming message input stream is null
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(Transport
Utils.java:64)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO
peration.java:368)
at
org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvo
cationWorker.run(OutInAxisOperation.java:431)
... 3 more
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.711 sec
I inspect the soap envelope right before it is handed to the axis engine to
send in the server's callback target invoker and this is what it looks like
(which looks fine to me):
Axis2ServiceCallbackTargetInvoker.invokeTarget, responseOM:
<axis2ns1:getGreetin
gsCallback xmlns:axis2ns1="http://helloworld";><axis2ns2:getGreetingsReturn
xmlns
:axis2ns2="http://helloworld";>Alo
John</axis2ns2:getGreetingsReturn></axis2ns1:g
etGreetingsCallback>
Since the client exception occurs in axis, it would seem as if axis is not
sending the message correctly. But since you say that the callback is
finished without exceptions, I am not sure what to think. The way I read
what you say, you are not getting the exception above, which makes me think
axis /is/ sending the message correctly and we just may not be running the
test exactly the same.
But if you do get the exception above, then we'd need to see if either axis
is not being configured correctly to send the response from the server, or
there'd may be a remote possibility that axis is not working as advertised.
So, can you let me know if what I see on the client is what you see?
Thanks
----- Original Message -----
From: "Raymond Feng" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, October 06, 2006 9:09 PM
Subject: Got one path working for the server-side web service async with
callback
Hi, Ignacio.
I managed to get the helloworldws-async sample working. I can see both the
request and callback are finished without exceptions.
I had to fix some issues in the core as well as the test case.
1) Replaced some logic on ServiceContract.getCallbackClass() which is
java-centric
2) Fixed the wrong usages of operation in the JDKWireService (in some cases,
we use the source operation for the target side)
3) Replaced "interface.java" with "interface.wsdl" and fixed some issues in
the wsdl file. It's the same workaround as we did on the client side that we
have to force the axis2 service to use WSDL interface so that data
transformation is triggered.
I'll commit the changes and you can verify it.
BTW, I'm still seeing the "null repsonse" from the client.
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
