SoapAction is *usually* prefaced with urn: as seen here
operation.setSoapAction("urn:" + opName);so servicePath is incorrect check ServicesDirectory attribute in axis2.xml servicePath attribute in axis2.xml also Make sure your EPR is valid M-- ----- Original Message ----- From: Iyengar, Kumar To: [email protected] Sent: Tuesday, November 13, 2007 8:54 PM Subject: RE: Dynamic web services Also, I get an error "Unable to parse request URL [urn:testWS2][/arsys/services]". I get this error whether I have a service.xml file or not. The URL that I pass in to my application is http://zzz:8080/arsys/services/ARService?server =xxx&WebService=yyy Has anyone seen this error? --kumar ------------------------------------------------------------------------------ From: Iyengar, Kumar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 4:31 PM To: [email protected] Subject: Dynamic web services Hi all, We use Axis in a non standard way. The typical use of Axis is where one generates the java stubs and then populates the stubs and deploys the application. In our application we do it a bit dynamically - we have a generic service and when the request comes in, it takes the request and then extracts the document, determines the operation and makes internal api calls. This way we never generate stubs. I am currently upgrading our setup from Axis to Axis2 and having problems with it: 1) I tried creating a service.xml file specifying the 'ServiceClass' name. However, it is not clear whether I need to specify the method name. With Axis I could specify the method name in the wsdd file. 2) Is there a complete documentation that explains all the options that can be specified in a service.xml? I have only found links (especially in IBM developer network) that explain bits and pieces. 3) Also, is it OK not to specify any operation in the service.xml file? What I really want is my code to take control of the Message Context and then extract the document and operation and then make internal calls. 4) if none of that work then do I have to do this by writing my own handler? I hope that is not the case since I could do this very easily with Axis. Any help is greatly appreciated. --kumar
