Hi Clarence,
I actually started out with rpc/encoded but had to switch to
document/literal wrapped to get interoperability with .NET, as it
doens't really support rpc style very well at all. One particular
problem I had was with 2D arrays, which .NET clients couldn't interpret
at all. Don't know if this will affect you, but maybe something to be
aware of.
Richard.
Clarence Dahlin wrote:
Thanks Richard,
I'll have a look at that. My service is also document/wrapped (though
I will most likely have to change that to rpc/literal due to the fact
that the community I'm working with wanted rpc/literal).
I'm actually using VS .NET 2005 with Framework 2.0, but it still might
be the same problem.
/ Clarence
On 11/15/05, *Richard Gregory* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Clarence,
I'm really just a .NET novice (and I wouldn't claim to be an expert in
axis or web services either) - I think I'm probably in the same
position
as you, in that I'm really only using it to test interoperability
with
my Axis services.
I had a few problems with .NET clients because I found when generating
the .NET (i'm using .NET 1.1) Reference.cs proxy classes, that visual
studio doesn't interpret the wsdl files in the same way as
wsdl2java (my
services are document/literal wrapped, by the way), and therefore
wasn't
interpreting the returned message correctly. I had to edit the
Reference.cs to add some classes which reflected the objects that axis
was sending, and ensure that the correct object types where being
returned by my proxy classes.
If the soap message being returned to your .NET client is correct (the
same as is returned to an axis client), you could check your
reference.cs and see if you have the same problem.
I'm just guessing here, but I hope this is of some help to you.
Richard.
Clarence Dahlin wrote:
> Ok I see. Then it shouldn't cause any problems, just as Richard
said.
> I have to investigate further to see why it doesn't work with VS
.NET.
>
> Thank you Toshiyuki and Yves.
>
> On 11/15/05, *Toshiyuki Kimura* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> Hi Clarence and Richard,
>
> It's valid transfer encoding - 'chunked' which is
> specified in HTTP 1.1 [RFC-2616].
> < http://www.w3.org/Protocols/rfc2616/rfc2616.html
> <http://www.w3.org/Protocols/rfc2616/rfc2616.html>>
>
> Thanks,
> Toshi
>
> On Tue, 15 Nov 2005, Richard Gregory wrote:
>
> > Hi Clarence,
> >
> > I get these random numbers in my http when I connect
> > to my axis service with .NET clients. I'm not sure
> > where they come from or why, but they don't seem to
> > have any effect on the clients, which work perfectly.
> >
> > Richard.
> >
> > Clarence Dahlin wrote:
> >
> >> I've almost only used Axis for both client and server, but I
> also need to
> >> verify that my service works with Visual Studio and other
toolkits.
> >>
> >> I receive a somewhat puzzling HTTP Response when I've called
> the service on
> >> Axis from a C# client in Visual Studio .NET.
> >>
> >> I'm not getting the connectReturn to my client.
> >>
> >> Does anyone know where the numbers 177 and 0 appears from and
> why? Could
> >> they mess up things for my client?
> >>
> >> HTTP/1.1 200 OK
> >> Content-Type: text/xml;charset=utf-8
> >> Transfer-Encoding: chunked
> >> Date: Tue, 15 Nov 2005 09:34:27 GMT
> >> Server: Apache-Coyote/1.1
> >>
> >> 177
> >> <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope
> >> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/
> <http://schemas.xmlsoap.org/soap/envelope/>"
> >> xmlns:xsd=" http://www.w3.org/2001/XMLSchema";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> < http://www.w3.org/2001/XMLSchema-instance>"
> >>
>
<http://www.w3.org/2001/XMLSchema-instance%22>><soapenv:Body><connectResponse
> >> xmlns=" xxxi.xxx.se <http://xxxi.xxx.se> <http://xxxi.xxx.se>
> >>
> <http://xxxi.xxx.se
<http://xxxi.xxx.se>>"><connectReturn>c017e9/107931de21a//7ff8</connectReturn></connectResponse></soapenv:Body></soapenv:Envelope>
>
> >> 0
> >
> >
> >
>
>
