Re: How to connect to server with dotnet client
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 [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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to connect to server with dotnet client
On Jan 29, 2008 6:08 PM, Gavan Hood [EMAIL PROTECTED] wrote: 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, If you can download http://people.apache.org/dist/axis2/nightly/, it is always better to check with the latest updates. Thanks Dimuthu 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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.
