[jboss-user] [JBossWS] - jaxrpc interop

I have a recalcitrant client that seems to insist on stripping the Namespace from the rpc request. I'm testing the JBossWS 1.0.3 rpcstyle sample. When deployed on Tomcat, the service does not seem to care about the missing namespace. JBossWS throws a SOAP Fault. I'm afraid I'm not familiar with the intricacies of method dispatching. Is there any way to redeploy this service on JBossWS so that it can tolerate this missing namespace? Here's a request from soapui, which includes xmlns:rpc and returns a valid response: | 2006-11-02 14:24:19,597 DEBUG [jbossws.SOAPMessage] Incomming SOAPMessage | <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' | xmlns:rpc='http://org.jboss.ws/samples/rpcstyle'> | <soapenv:Header/> | <soapenv:Body> | <rpc:purchase> | <String_1 xmlns=''>Hello</String_1> | <String_2 xmlns=''>There</String_2> | </rpc:purchase></soapenv:Body></soapenv:Envelope> | 2006-11-02 14:24:19,598 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: {http://org.jboss.ws/samples/rpcstyle}purchase | And here's the request from the careless client, which results in an Exception: 2006-11-02 14:24:45,217 DEBUG [org.jboss.ws.server.StandardEndpointServlet] doPost: /jbossws-samples-rpcstyle | 2006-11-02 14:24:45,217 DEBUG [org.jboss.ws.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.soap.SOAPMessageContextImpl@bd0da3 | 2006-11-02 14:24:45,218 DEBUG [org.jboss.ws.server.ServiceEndpoint] BEGIN handleRequest: jboss.ws:context=jbossws-samples-rpcstyle,endpoint=TrivialEndpoint | 2006-11-02 14:24:45,219 DEBUG [org.jboss.ws.soap.MessageFactoryImpl] createMessage: [contentType=text/xml] | 2006-11-02 14:24:45,220 DEBUG [org.jboss.ws.soap.SOAPContentElement] setXMLFragment: <String_1 xmlns=''>Kermit</String_1> | 2006-11-02 14:24:45,221 DEBUG [org.jboss.ws.soap.SOAPContentElement] setXMLFragment: <String_2 xmlns=''>Ferrari</String_2> | 2006-11-02 14:24:45,221 DEBUG [jbossws.SOAPMessage] Incomming SOAPMessage | | <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'> | <SOAP-ENV:Header/> | <SOAP-ENV:Body> | <purchase> | <String_1 xmlns=''>Kermit</String_1> | <String_2 xmlns=''>Ferrari</String_2> | </purchase></SOAP-ENV:Body> | </SOAP-ENV:Envelope> | 2006-11-02 14:24:45,221 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: null | 2006-11-02 14:24:45,222 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: null | 2006-11-02 14:24:45,222 DEBUG [javax.xml.rpc.soap.SOAPFaultException] new SOAPFaultException [code={http://schemas.xmlsoap.org/soap/envelope/}Client,string=Endpoint {http://org.jboss.ws/samples/rpcstyle}TrivialServicePort does not contain operation meta data for: purchase,actor=null,detail=null] | 2006-11-02 14:24:45,222 ERROR [org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper] SOAP request exception | javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://org.jboss.ws/samples/rpcstyle}TrivialServicePort does not contain operation meta data for: purchase | at org.jboss.ws.server.ServiceEndpointInvoker.getDispatchDestination | ... | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982812#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...