Hello
I now have a straight method which gets called, returns on the
server-side, but the client is never notified.After a while, the
client outputs:
at
org.apache.axis2.description.OutInAxisOperationClient$SyncCallBac
k.waitForCompletion(OutInAxisOperation.java:497)
at
org.apache.axis2.d
In your services.xml file, you need to add an additional:
http://www.w3.org/2004/08/wsdl/in-only";
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"
/>
for every one of your void methods. Failure to do so, will result
in them not being called. I ask the Axis2 development tea
Hi Everyone
For people experiencing the same behaviour, it turns out this is
a rather severe bug in Axis2 1.5 and Axis2 1.5.1. To be honest,
its so severe, I wonder whether the Axis2 framework was tested at
all before it went out the door. I lost eight hours due to the
problem. You need to:
On S
I modified one of the methods to return a value instead of void
and it was called. Then I changed another so that it did not
throw an Axis Fault and it too could be called. The problem is I
have a large API and I need these method signatures to stay the
same. Any ideas, why Axis is not calling the
Hi Amila
As suggested, I tested it on the setMilterEnabled function.
Here is the request:
http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing";>http://ws.apache.org/namespaces/axis2";
wsa:IsReferenceParameter="true">urn:uuid:3A7414531B3A0DDCA4126728
3377155http://loca
use tcpmon[1] to check whether there is a problem with the request or you
get any error response.
is there any errors in the server console?
Amila.
[1] http://ws.apache.org/commons/tcpmon/
On Sat, Feb 27, 2010 at 4:26 PM, jamie wrote:
> Greetings!
>
> I am having problems with Axis2. Some of t
