Hi Dimuthu, I agree totallly, I have been working on that today, basically the dotnet client formats the soap message so you cannot change that side. Which is understandable as a client should not have to know knowlede of how the service is stored on the server. So I tried to configure Axis2 to locate the / directory and locate the TestData folder under it. I could not find a way to do that. Do you know of a way to do that? In summary: The axis server should not force the path to have /axis2/services prefix... how do remove that ? Thanks Gavan
Dimuthu Gamage <[EMAIL PROTECTED]> wrote: Hi Gavan, If you recieve service not found error from axis2/c server, it can be mostly due to the wrong endpoint. If your service directory is "TestData" ( i.e. inside the axis2 services directory) your service endpoint should be "http://your_host_name:port/axis2/services/TestData";. I can see in your fault you have set the endpoint to "http://127.0.0.1:8080/TestData";. Can you try with "http://127.0.0.1:8080/axis2/services/TestData"; as the service endpoint? Thanks, Dimuthu On Jan 30, 2008 4:06 AM, Gavan Hood wrote: > > I renamed my previous post as the problem in my opinion is in the Axis2 C > http server capabilities, which may be a design flaw. The server responds > with a service not found error as it is unable to identify the correct > > The original post is below the tcpmon trace that follows. I am about to see > what I can do to identify how the http server handles the http header and > locates the service... the microsoft namespace QName looks different to what > I see in the echo test.... which I appended to end of the message after the > original text > > POST /TestData HTTP/1.1 > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client > Protocol 2 > .0.50727.1366) > VsDebuggerCausalityData: > uIDPo7iwHfJnmU1MsR+ixSBkQ/wAAAAAIcBQpWIKEkiCDjuzhhBtsBm > dJpxYAh9KiKHDv3dFhhcACQAA > Content-Type: text/xml; charset=utf-8 > SOAPAction: "http://software.mytest.com/GetData"; > Host: localhost:9090 > Content-Length: 428 > Expect: 100-continue > Connection: Keep-Alive > > xmlns:soap="http://schemas. > xmlsoap.org/soap/envelope/" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance > " xmlns:xsd="http://www.w3.org/2001/XMLSchema";>> xmlns="http:/ > /software.mytest.com/">localhostsampl > esAerationfalse > â > RETRIEVING DATA.. > /* retrieving time = 17:36:27*/ > /* time throughput = 0 sec(s)*/ > --------------------- > HTTP/1.1 500 Internal Server Error > Content-Type: text/xml;charset=UTF-8 > Connection: Keep-Alive > Content-Length: 404 > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>> > > penv:Header/>soapenv:Server< > faultstring>Service Not FoundService Not > Found, > Endpoint referance address is http://127.0.0.1:8080/TestData and wsa acti > ons is > (null)> ope> > > > > > > Gavan Hood wrote: > > I suspected a problem with MS support for WS basic profile as opposed to WS* > indicated in Axis2C. I hoped there would be a solution but have not found > anything. I am at a point where I need to tweak on of the two worlds... or > drop Axis2. I still hope there is something I am missing that will let the > following process work for me... Let me know your thoughts please. > I have to generate a service that is equivalent to a asmx service that has > dotnet clients, once I get that I can then extend... > I know the MS and non MS worlds like to live in isolation, unfortunately I > am in world that demands they work together. > > > I started with a dotnet asmx web service.... generated its WSDL this was to > be the base for the service environemnt. > I then processed the WSDL with WSDL2C from Axis2 to give the C skeleton. > > I then compiled the skeleton (by modifying the echo sample makefile ...) > With the dll etc in the Services folder, I can see it in the default 9090 > connection of listed services (which I think is just a dump of the xml > folder contents). > > I autogenerated a C# client with MS visual studio from the WSDL. It worked > fine with the .asmx file as you would expect. > I then pointed it at the Axis2 server and watched the SOAP packets with > tcpmon, I can see a significant difference in the format as expected. > I now need to identify if there are: > A settting for Microsoft tools to connect to the Axis2C server. > A configuration setting to Axis2C server to handle dotnet clients as above > > If there is no simple change, is there a code change for the Axis2C server > to trap these connections and translater them. I am guessing I either have > to make a custom http handler or maybe there is a WS basic profile to WS* > conversion utility that works like tcpmon.... > > Any help much appreciated... > > > > > > > > ________________________________ > Never miss a thing. Make Yahoo your homepage. > > POST /axis2/services/echo HTTP/1.1 > User-Agent: Axis2/C > Content-Length: 512 > Content-Type: application/soap+xml;charset=UTF-8 > Host: localhost:9090 > > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>> nv:Header > xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://localh > ost:9090/axis2/services/echohttp://ws.apache.org/axis2/c/sa > mples/echoString1b41e04d-25c6-45ba-8ced-88241f4a6160 > > xmlns:ns1="http:/ > /ws.apache.org/axis2/services/echo">Hello > World!> soapenv:Body>Ã¥â5\/â» > RETRIEVING DATA.. > /* retrieving time = 17:37:32*/ > /* time throughput = 0 sec(s)*/ > --------------------- > HTTP/1.1 200 OK > Content-Type: application/soap+xml;charset=UTF-8 > Content-Length: 672 > > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>> nv:Header > xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://ws > .apache.org/axis2/c/samples/echoStringhttp:/ > /localhost:9090/axis2/services/echo220f9 > b62-4535-4e35-9208-1c0043b6edb3> wsa:RelationshipTy > pe="http://www.w3.org/2005/08/addressing/reply";>1b41e04d-25c6-45ba-8ced-88241f4a > 6160> xmlns:ns1="ht > tp://ws.apache.org/axis2/c/samples">Hello > World!> soapenv:Body> > > > ________________________________ > Never miss a thing. Make Yahoo your homepage. --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
