Re: long vs. Long
Simon Fell a écrit : -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane) Sent: Monday, November 29, 2004 7:20 PM To: [EMAIL PROTECTED] Subject: Re: long vs. Long If anyone else has an example on how to get the Long stuff to work end-to-end and to interoperate with .NET I would love to see it (it has to be RPC not doc/lit) as it would be nice to make use of the nillable property ... Thanks. Tim The long type in .NET is not nullable, so trying to send it as a nil over the wire is just going to result in headaches for the .NET folks. The long type in Java is not nullable either... The Long type is. But I don't know .Net at all. -- Julien
RE: long vs. Long
-Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim K. (Gmane) Sent: Monday, November 29, 2004 7:20 PM To: [EMAIL PROTECTED] Subject: Re: long vs. Long If anyone else has an example on how to get the Long stuff to work end-to-end and to interoperate with .NET I would love to see it (it has to be RPC not doc/lit) as it would be nice to make use of the nillable property ... Thanks. Tim The long type in .NET is not nullable, so trying to send it as a nil over the wire is just going to result in headaches for the .NET folks. Cheers Simon
Re: long vs. Long
If anyone else has an example on how to get the Long stuff to work end-to-end and to interoperate with .NET I would love to see it (it has to be RPC not doc/lit) as it would be nice to make use of the nillable property ... Thanks. Tim The long type in .NET is not nullable, so trying to send it as a nil over the wire is just going to result in headaches for the .NET folks. Cheers Simon Ah, thanks for clarifying it. I love .NET, how we have to bastardize our web services just to make them work with .NET ... Tim
Re: long vs. Long
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should
have a nillable='true' attribute, otherwise I guess it's a bug in
the WSDL-generation part (Java2WSDL).
If it has this attribute, then the bug is in the client-side code
(WSDL2Java).
For a method:
Long b(Long id) throws CustomException { ... }
Here's the WSDL snippet generated by Java2WSDL:
wsdl:message name=bRequest
wsdl:part name=in0 type=xsd:long/
/wsdl:message
wsdl:message name=bResponse
wsdl:part name=bReturn type=xsd:long/
/wsdl:message
So Long is mapped to xsd:long but it's NOT declaraed nillable. Is this
the bug?
I think so. Which version of Axis do you use ?
Axis 1.2RC1
Or should the Long have been mapped to soapenc:long instead which is
not compatible with .NET?
xsd:long and soapenc:long should be the same thing (IIRC the soap
encoding spec defines soapenc:long as xsd:long).
Is xsd:long nillable=true compatible with .NET?
I don't know :) It should but...
I'll just use the primitive long, at least I know that works ...
If anyone else has an example on how to get the Long stuff to work
end-to-end and to interoperate with .NET I would love to see it (it has
to be RPC not doc/lit) as it would be nice to make use of the nillable
property ...
Thanks.
Tim
Re: long vs. Long
Tim Gmane a écrit :
WAJSBERG Julien RD-BIZZ wrote:
Tim Dev a écrit :
Hi,
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should
have a nillable='true' attribute, otherwise I guess it's a bug in
the WSDL-generation part (Java2WSDL).
If it has this attribute, then the bug is in the client-side code
(WSDL2Java).
For a method:
Long b(Long id) throws CustomException { ... }
Here's the WSDL snippet generated by Java2WSDL:
wsdl:message name=bRequest
wsdl:part name=in0 type=xsd:long/
/wsdl:message
wsdl:message name=bResponse
wsdl:part name=bReturn type=xsd:long/
/wsdl:message
So Long is mapped to xsd:long but it's NOT declaraed nillable. Is this
the bug?
I think so. Which version of Axis do you use ?
Or should the Long have been mapped to soapenc:long instead which is
not compatible with .NET?
xsd:long and soapenc:long should be the same thing (IIRC the soap
encoding spec defines soapenc:long as xsd:long).
Is xsd:long nillable=true compatible with .NET?
I don't know :) It should but...
--
Julien
Re: long vs. Long
WAJSBERG Julien RD-BIZZ wrote:
Tim Dev a écrit :
Hi,
I have a simple test method:
Long foo(Long bar)
Java2WSDL maps the Long to xsd:long and the client stub contains the
method as:
long foo(long bar)
How does the WSDL look like ? The parameter and return value should have
a nillable='true' attribute, otherwise I guess it's a bug in the
WSDL-generation part (Java2WSDL).
If it has this attribute, then the bug is in the client-side code
(WSDL2Java).
For a method:
Long b(Long id) throws CustomException { ... }
Here's the WSDL snippet generated by Java2WSDL:
wsdl:message name=bRequest
wsdl:part name=in0 type=xsd:long/
/wsdl:message
wsdl:message name=bResponse
wsdl:part name=bReturn type=xsd:long/
/wsdl:message
So Long is mapped to xsd:long but it's NOT declaraed nillable. Is this
the bug?
Or should the Long have been mapped to soapenc:long instead which is not
compatible with .NET?
Is xsd:long nillable=true compatible with .NET?
Thanks for your help.
Tim
Re: long vs. Long
Tim Dev a écrit : Hi, I have a simple test method: Long foo(Long bar) Java2WSDL maps the Long to xsd:long and the client stub contains the method as: long foo(long bar) How does the WSDL look like ? The parameter and return value should have a nillable='true' attribute, otherwise I guess it's a bug in the WSDL-generation part (Java2WSDL). If it has this attribute, then the bug is in the client-side code (WSDL2Java). -- Julien
