Hi and thank you for the response. I just looked through the code and could see that the client claims to use XML-RPC. That's the reason for the non well formed XML. So I think to write a mobile client on my own unless I find another framework...
-----Original Message----- From: Glen Mazza [mailto:[email protected]] Sent: Thursday, April 02, 2009 2:28 PM To: [email protected] Subject: Re: SoapFault: No namespace on "methodCall" element (Disable validation possible?) That XML sample isn't well-formed. Is there a reason why you can't provide a namespace on the methodCall element? It wouldn't appear very safe if we would allow CXF to function purely on the element names without taking into consideration the namespaces. Glen Timon Grtzmacher wrote: > > Hi everybody, > > > > I?m trying to access a simple CXF webservice from a mobile application. > > The webservice is published from a servlet extending the > CXFNonSpringServlet > on tomcat. > > The sayHello method I wrote is not called at all because an interceptor > throws following exception: > > org.apache.cxf.binding.soap.SoapFault: No namespace on "methodCall" > element > > > > The mobile client sends simple XML like <?xml > version=\"1.0\"?><methodCall><methodName>sayHello</methodName>? > > > > Is there a possibility to disable validation or any other way to get > around > this? > > > > Thanks for any hint in advance! > > > > Timon > -- View this message in context: http://www.nabble.com/SoapFault%3A-No-namespace-on-%22methodCall%22-element-%28Disable-validation-possible-%29-tp22845827p22846717.html Sent from the cxf-user mailing list archive at Nabble.com.
