Re: Axis C server support for dotnet client
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/wAIcBQpWIKEkiCDjuzhhBtsBm 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 faultstringService 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
Re: Axis C server support for dotnet client
I managed to get the path to the Service to be /axis2/services/TestData in the client. Even though this is not a usable solution for production it did enable the server to locate the service, it then generated another set of errors which I am looking at now... I still need to work out how to get the server to not require the prefix... but at least I can find the service.. even if it wont run yet... Gavan Hood [EMAIL PROTECTED] wrote: 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/wAIcBQpWIKEkiCDjuzhhBtsBm 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 faultstringService 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
How to connect to server with dotnet client
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.
Re: How to connect to server with dotnet client
Thanks for your response... I have inspected the messages, the SOAP envelope transmitted. The theory of interop assumes that the semantics of the SOAP encoding is consistent or can be understood by sender and reciever. I would have thought that the Axis2 team would have considered what is one of the largest code bases in place when designing and there will be a solution available. As far as I can tell the dotnet client does not use the WS* syntax, thus the Axis2 does not identify / decode the message correctly. Either the dotnet client has a setting to support WS* or alternatively the Axis2 server has a setting to support WS basic profile 1. I cannot find a setting in either of the two. I used the 1.3 build, however I don't think the issue will be there as that is the service framework generator. I do not believe the Axis2C server is even calling the service at all as it is not decoding the message due to aforementioned problems. Dimuthu Gamage [EMAIL PROTECTED] wrote: Hi, AFAIK there is no special configuration that you can set to interop with C#. Since by theory web services should be interop with any correct implementations. That can probably be a bug in WSDLC code. Next my usual question:) what is the version of WSDL2C you are trying, is that Java 1.3 or the nightly build? If you haven't try nightly build your problem may have fixed in there.. http://people.apache.org/dist/axis2/nightly/, otherwise please send us the WSDL or just the schema. we may able to track the problem. Thanks Dimuthu On Jan 29, 2008 3:09 PM, 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Looking for last minute shopping deals? Find them fast with Yahoo! Search.
Axis C server support for dotnet client
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/wAIcBQpWIKEkiCDjuzhhBtsBm 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 ?xml version=1.0 encoding=utf-8?soap:Envelope 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;soap:BodyGetData xmlns=http:/ /software.mytest.com/serverNamelocalhost/serverNameareaNamesampl es/areaNamegroupNameAeration/groupNamebHistoryfalse/bHistory/GetData /soap:Body/soap:Envelope#9668; 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 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soa penv:Header/soapenv:Bodysoapenv:Faultfaultcodesoapenv:Server/faultcode faultstringService Not Found/faultstringdetailExceptionService Not Found, Endpoint referance address is http://127.0.0.1:8080/TestData and wsa acti ons is (null)/Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envel ope Gavan Hood [EMAIL PROTECTED] 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 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soape nv:Header xmlns:wsa=http://localh'http://www.w3.org/2005/08/addressing;wsa:Tohttp://localh ost:9090/axis2/services/echo/wsa:Towsa:Actionhttp://ws.apache.org/axis2/c/sa mples/echoString/wsa:Actionwsa:MessageID1b41e04d-25c6-45ba-8ced-88241f4a6160 /wsa:MessageID/soapenv:Headersoapenv:Bodyns1:echoString xmlns:ns1=http:/ /ws.apache.org/axis2/services/echotextHello World!/text/ns1:echoString/ soapenv:Body/soapenv:Envelopeå#9496;5\/#9787; 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 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soape nv:Header xmlns:wsa=http://ws'http://www.w3.org/2005/08/addressing;wsa:Actionhttp://ws
running samples
I have built the 1.2 version and built the samples a few times now, When I build the samples I get the client code created but cannot see where server code is deployed. When I hit the 9090 URL it shows a heading for installed services and nothing more. When I run any of the clients they report erros such as math stub invoke Failed for math, Error creating service client Please check AXIS2c_HOME (which I have tried a few variations on), I get same text for yahoo and google samples. What exactly should happen when a service is created and deployed, what is the sequence of actions that I should see. Where should the service end up. Is there documentation on this, what I have found so far does not clearly indicate what should happen. thanks - Never miss a thing. Make Yahoo your homepage.
locating / building minamilist config for jre 1.4.2
I tried to find the minimalist build for axis 2 but could not locate it anywhere, can someone point me to that please? I build on pc with setting for jre1.4 in eclipse and use the jars in an embedded system. In eclipse I just set the jre build level to 1.4 and thats fine Is there a setting did not see anything on that in the axis2 build scripts... I need to be able support soap based web service on tomcat 5.5 on embedded debian linux and be able to act as client. If there is a specific set of jars I can build even less than the avertised minamilist build that woud be great... do you know what i would need ? Thanks Gavan - Looking for last minute shopping deals? Find them fast with Yahoo! Search.
