Are you saying that scope="soapsession" does not any longer work in AXIS2 1.5.1?
Josef.Stadelmann @axa-winterthur.ch Von: jamie [mailto:jam...@fastmail.fm] Gesendet: Samstag, 27. Februar 2010 20:25 An: java-user@axis.apache.org; java-user@axis.apache.org Betreff: Re: Methods Not Called 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 Sat, 27 Feb 2010 17:18 +0200, "jamie" <jam...@fastmail.fm> wrote: 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 methods? On Sat, 27 Feb 2010 17:13 +0200, "jamie" <jam...@fastmail.fm> wrote: Hi Amila As suggested, I tested it on the setMilterEnabled function. Here is the request: <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing";><axis2:ServiceGroupId xmlns:axis2="http://ws.apache.org/namespaces/axis2"; wsa:IsReferenceParameter="true">urn:uuid:3A7414531B3A0DDCA41267283377155 </axis2:ServiceGroupId><wsa:To>http://localhost:8070/test/services/Confi g</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing /none</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:5699C4CE65CF3AD 3D31267283394942</wsa:MessageID><wsa:Action>urn:setMilterServerEnable</w sa:Action></soapenv:Header><soapenv:Body><ns2:setMilterServerEnable xmlns:ns2="http://webservice.archiva.stimulus.com";><ns2:enable>false</ns 2:enable></ns2:setMilterServerEnable></soapenv:Body></soapenv:Envelope> The response is: HTTP/1.1 202 Accepted Server: Apache-Coyote/1.1 Content-Length: 0 Date: Sat, 27 Feb 2010 15:09:54 GMT Can you interpret the above for me? This call looks like it is being accepted by tomcat, but the method on the server is never actually called. Any further ideas? Jamie On Sat, 27 Feb 2010 19:17 +0530, "Amila Suriarachchi" <amilasuriarach...@gmail.com> wrote: 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 <jam...@fastmail.fm> wrote: Greetings! I am having problems with Axis2. Some of the methods in my web services server API are simply not being called by my test client. It seems as if Axis2 does not bother to execute the methods at all. No error is returned. When the client called the method: ConfigStub.TestWS testws = new ConfigStub.TestWS(); testws.setId(id); ConfigStub.EditTest editTest = new ConfigStub.EditTest(); editVolume.setTestWS(testws); configStub.editTest(editTest); The method editTest(..) is just not called at all, despite the fact that there are other methods that are successfully called and there is no significant different in the way the methods are defined. There is no error returned by Axis2. Here is my services.xml file: <serviceGroup> <service name="Search" scope="soapsession"> <Description> search API </Description> <messageReceivers> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> </messageReceivers> <parameter name="ServiceClass" locked="false">com.webservice.SearchAPI</parameter> </service> <service name="Config" scope="soapsession"> <Description> config API </Description> <messageReceivers> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> </messageReceivers> <parameter name="ServiceClass" locked="false">com..webservice.ConfigAPI</parameter> </service> <service name="Status" scope="soapsession"> <Description> configure status </Description> <messageReceivers> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> </messageReceivers> <parameter name="ServiceClass" locked="false">com.webservice.StatusAPI</parameter> </service> </serviceGroup> Any help would be most appreciated Jamie -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
