You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Gavan Hood <oo...@yahoo.com> on 2008/01/29 10:39:14 UTC

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: Axis "C" server support for dotnet client

Posted by Samisa Abeysinghe <sa...@wso2.com>.
Gavan Hood wrote:
> 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...

http://wso2.org/library/2663

Thanks,
Samisa...


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Re: Axis "C" server support for dotnet client

Posted by Gavan Hood <oo...@yahoo.com>.
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 <oo...@yahoo.com> 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 <di...@gmail.com> 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.

       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.

Re: Axis "C" server support for dotnet client

Posted by Gavan Hood <oo...@yahoo.com>.
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 <di...@gmail.com> 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.

Re: Axis "C" server support for dotnet client

Posted by Dimuthu Gamage <di...@gmail.com>.
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 <oo...@yahoo.com> 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
> <?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:Body><GetData
> xmlns="http:/
> /software.mytest.com/"><serverName>localhost</serverName><areaName>sampl
> es</areaName><groupName>Aeration</groupName><bHistory>false</bHistory></GetData>
> </soap:Body></soap:Envelope>◄
> 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:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><
> faultstring>Service Not Found</faultstring><detail><Exception>Service 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 <oo...@yahoo.com> 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://www.w3.org/2005/08/addressing"><wsa:To>http://localh
> ost:9090/axis2/services/echo</wsa:To><wsa:Action>http://ws.apache.org/axis2/c/sa
> mples/echoString</wsa:Action><wsa:MessageID>1b41e04d-25c6-45ba-8ced-88241f4a6160
> </wsa:MessageID></soapenv:Header><soapenv:Body><ns1:echoString
> xmlns:ns1="http:/
> /ws.apache.org/axis2/services/echo"><text>Hello
> World!</text></ns1:echoString></
> soapenv:Body></soapenv:Envelope>å┘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
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soape
> nv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Action>http://ws
> .apache.org/axis2/c/samples/echoString</wsa:Action><wsa:From><wsa:Address>http:/
> /localhost:9090/axis2/services/echo</wsa:Address></wsa:From><wsa:MessageID>220f9
> b62-4535-4e35-9208-1c0043b6edb3</wsa:MessageID><wsa:RelatesTo
> wsa:RelationshipTy
> pe="http://www.w3.org/2005/08/addressing/reply">1b41e04d-25c6-45ba-8ced-88241f4a
> 6160</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:echoString
> xmlns:ns1="ht
> tp://ws.apache.org/axis2/c/samples"><text>Hello
> World!</text></ns1:echoString></
> soapenv:Body></soapenv:Envelope>
>
>
>  ________________________________
> Never miss a thing. Make Yahoo your homepage.

Axis-c client with JAX-WS service

Posted by Arseny <fo...@mail.ru>.
Hello!
I am trying to use axis-c c++ client with JAX-WS web service.
Call reaches its destination without any problems.
But then I have a response from the web service:

<?xml version="1.0" ?><S:Envelope 
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:changeIssueResponse 
xmlns:ns2="http://cardlibrary.webservices.integration.css.mycompany.com" 
xmlns:ns3="http://common.webservices.integration.css.mycompany.com"/></S:Body></S:Envelope>

which causes xerces_2_2::RuntimeException with following details:
 xercesc_2_2::XMLException    {
    fCode=Scan_BadPScanToken
    fSrcFile= 
"c:\xml4c_root\xerces-c-src2_2_0\src\xercesc\internal\IGXMLScanner.cpp"
    fSrcLine=294
    fMsg="The call to scanNext() is illegal at this time" }

That`s it. I was calling a simple operation using axis-generated C++ stubs.

May be anybody had an experience in connecting axis-c and jax-ws?




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Re: How to connect to server with dotnet client

Posted by Gavan Hood <oo...@yahoo.com>.
I have downloaded the source and will check it out, however as I mentioned, the problem is in Axis2- C not the java code... As far as I can tell the service is not being located due to the incompatability of the message formats.

Dimuthu Gamage <di...@gmail.com> wrote:  On Jan 29, 2008 6:08 PM, Gavan Hood 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 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: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
>
>
> ________________________________
> Looking for last minute shopping deals? Find them fast with Yahoo! Search.


       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.

Re: How to connect to server with dotnet client

Posted by Dimuthu Gamage <di...@gmail.com>.
On Jan 29, 2008 6:08 PM, Gavan Hood <oo...@yahoo.com> 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 <di...@gmail.com> 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: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
>
>
>  ________________________________
> Looking for last minute shopping deals? Find them fast with Yahoo! Search.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Re: How to connect to server with dotnet client

Posted by Gavan Hood <oo...@yahoo.com>.
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 <di...@gmail.com> 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: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org



       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.

Re: How to connect to server with dotnet client

Posted by Dimuthu Gamage <di...@gmail.com>.
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 <oo...@yahoo.com> 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: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Axis "C" server support for dotnet client

Posted by Gavan Hood <oo...@yahoo.com>.
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
  <?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:Body><GetData xmlns="http:/
/software.mytest.com/"><serverName>localhost</serverName><areaName>sampl
es</areaName><groupName>Aeration</groupName><bHistory>false</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:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><
faultstring>Service Not Found</faultstring><detail><Exception>Service 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 <oo...@yahoo.com> 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:To>http://localh
ost:9090/axis2/services/echo</wsa:To><wsa:Action>http://ws.apache.org/axis2/c/sa
mples/echoString</wsa:Action><wsa:MessageID>1b41e04d-25c6-45ba-8ced-88241f4a6160
</wsa:MessageID></soapenv:Header><soapenv:Body><ns1:echoString xmlns:ns1="http:/
/ws.apache.org/axis2/services/echo"><text>Hello 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:Action>http://ws
.apache.org/axis2/c/samples/echoString</wsa:Action><wsa:From><wsa:Address>http:/
/localhost:9090/axis2/services/echo</wsa:Address></wsa:From><wsa:MessageID>220f9
b62-4535-4e35-9208-1c0043b6edb3</wsa:MessageID><wsa:RelatesTo wsa:RelationshipTy
pe="1b41e04d-25c6-45ba-8ced-88241f4a'>http://www.w3.org/2005/08/addressing/reply">1b41e04d-25c6-45ba-8ced-88241f4a
6160</wsa:RelatesTo></soapenv:Header><soapenv:Body><ns1:echoString xmlns:ns1="ht
tp://ws.apache.org/axis2/c/samples"><text>Hello World!</text></ns1:echoString></
soapenv:Body></soapenv:Envelope>

       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.