Calling C#-Webservice from a java client

[Sascha Schmidt]

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha

[CG]

It's not hard to use .net webservice using Java Client. You just need to make
sure of some data type etc. other than that i did not have any problem. It
was very smooth.

"Sascha Schmidt" wrote:

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha

[Marvin Smit]

Hi,

to add a litte; Just don't be fooled by the toolkits. Like CG wrote;
your main concern will be the datatypes you expose over the wire
(in/out parameters & return values).

If you stick to the XSD definable types (i.o.w. RecordSet = .Net, not
XSD! don't use in WS) you should be fine.

Hope this helps,

Marvin Smit.

On Tue, 8 Nov 2005 18:41:02 -0800, "CG" <[e-mail]>
wrote:

It's not hard to use .net webservice using Java Client. You just need to make
sure of some data type etc. other than that i did not have any problem. It
was very smooth.

"Sascha Schmidt" wrote:

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha

[Mario Casas]

Hi.

I'm programing in Visual Fox Pro 9 and I have the same problem with Java
Cliet. I follow these recomendation, but the problem is the same. This is
part of my WSDL file:

<message name='Vivienda.recibirVivienda'>
<part name='cViviendaXML' type='xsd:string'/>
</message>

<message name='Vivienda.recibirViviendaResponse'>
<part name='Result' type='xsd:string'/>
</message>

The client in VFP9 and VB6, receive the answer correct. But the java client
receive a NULL answer.

Thanks
"Marvin Smit" wrote:

Hi,

to add a litte; Just don't be fooled by the toolkits. Like CG wrote;
your main concern will be the datatypes you expose over the wire
(in/out parameters & return values).

If you stick to the XSD definable types (i.o.w. RecordSet = .Net, not
XSD! don't use in WS) you should be fine.

Hope this helps,

Marvin Smit.

On Tue, 8 Nov 2005 18:41:02 -0800, "CG" <[e-mail]>
wrote:

It's not hard to use .net webservice using Java Client. You just need to make
sure of some data type etc. other than that i did not have any problem. It
was very smooth.

"Sascha Schmidt" wrote:

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha

[Marvin Smit]

Hi,

Is there any chance that the java client was written using a toolkit
that is causing the error? If all clients work, but the Java one
doesn't, i would start looking at the java toolkit that is used, not
the server.

Marvin Smit.

On Wed, 9 Nov 2005 16:33:44 -0800, "Mario Casas" <Mario
Ca***@discussions.microsoft.com> wrote:

Hi.

I'm programing in Visual Fox Pro 9 and I have the same problem with Java
Cliet. I follow these recomendation, but the problem is the same. This is
part of my WSDL file:

<message name='Vivienda.recibirVivienda'>
<part name='cViviendaXML' type='xsd:string'/>
</message>

<message name='Vivienda.recibirViviendaResponse'>
<part name='Result' type='xsd:string'/>
</message>

The client in VFP9 and VB6, receive the answer correct. But the java client
receive a NULL answer.

Thanks
"Marvin Smit" wrote:

Hi,

to add a litte; Just don't be fooled by the toolkits. Like CG wrote;
your main concern will be the datatypes you expose over the wire
(in/out parameters & return values).

If you stick to the XSD definable types (i.o.w. RecordSet = .Net, not
XSD! don't use in WS) you should be fine.

Hope this helps,

Marvin Smit.

On Tue, 8 Nov 2005 18:41:02 -0800, "CG" <[e-mail]>
wrote:

>It's not hard to use .net webservice using Java Client. You just need to make
>sure of some data type etc. other than that i did not have any problem. It
>was very smooth.
>
>"Sascha Schmidt" wrote:
>
>> Hi again!
>>
>> Well, the first part of my "mission" (calling remoting objects from a
>> webservice) is solved. But there's another part: Calling
>> this C#-Webservice from a java client.
>>
>> Is this a difficult task? Or is this quite easy, like just a few lines
>> of source and using some of the packages from apache.org?
>> Has anybody done this before and will like to tell me about his/her
>> experiences?
>>
>> Thanks in advance!
>> Sascha
>>

[Jerry Pisk]

There's more to it, even sticking to XSD does not guarantee
interoperability. I have found that deriving types using complex type
extensions does not work cross-platform - .Net uses the default namespace
for its messages and jax-rpc ri chokes on that, it expects all namespaces to
be prefixed (it does not resolve the value of xsi:type in the default
namespace). Also .Net does not handle nillable types well, you need to
define them with minoccurs set to 0, if you set minoccurs to 1 and nillable
to true .Net 1.1 (but not 2.0) will throw during deserialization. There's
probably more then this.

Jerry

"Marvin Smit" <ma*********@gmail.com> wrote in message
news:g4********************************@4ax.com...

Hi,

to add a litte; Just don't be fooled by the toolkits. Like CG wrote;
your main concern will be the datatypes you expose over the wire
(in/out parameters & return values).

If you stick to the XSD definable types (i.o.w. RecordSet = .Net, not
XSD! don't use in WS) you should be fine.

Hope this helps,

Marvin Smit.

On Tue, 8 Nov 2005 18:41:02 -0800, "CG" <[e-mail]>
wrote:

It's not hard to use .net webservice using Java Client. You just need to
make
sure of some data type etc. other than that i did not have any problem. It
was very smooth.

"Sascha Schmidt" wrote:

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha

[Marvin Smit]

Hi,

reading the specs of the WS-I stuff, it are the toolkits that are
failing us, not the XSD usage in WebServices by itself.

That does not help us in the real world out there since there are only
so many toolkits that are 'accepted' and usable.

There are some 'validation tools' out there. My advise is still to
build up from the contracts (WSDL, XSD) and have the toolkits generate
the code. Its the best option between "code first->gen contracts->gen
code" and "contract first->gen server/client code".

Marvin Smit.

On Tue, 15 Nov 2005 11:57:51 -0800, "Jerry Pisk"
<je******@hotmail.com> wrote:

There's more to it, even sticking to XSD does not guarantee
interoperability. I have found that deriving types using complex type
extensions does not work cross-platform - .Net uses the default namespace
for its messages and jax-rpc ri chokes on that, it expects all namespaces to
be prefixed (it does not resolve the value of xsi:type in the default
namespace). Also .Net does not handle nillable types well, you need to
define them with minoccurs set to 0, if you set minoccurs to 1 and nillable
to true .Net 1.1 (but not 2.0) will throw during deserialization. There's
probably more then this.

Jerry

"Marvin Smit" <ma*********@gmail.com> wrote in message
news:g4********************************@4ax.com.. .

Hi,

to add a litte; Just don't be fooled by the toolkits. Like CG wrote;
your main concern will be the datatypes you expose over the wire
(in/out parameters & return values).

If you stick to the XSD definable types (i.o.w. RecordSet = .Net, not
XSD! don't use in WS) you should be fine.

Hope this helps,

Marvin Smit.

On Tue, 8 Nov 2005 18:41:02 -0800, "CG" <[e-mail]>
wrote:

It's not hard to use .net webservice using Java Client. You just need to
make
sure of some data type etc. other than that i did not have any problem. It
was very smooth.

"Sascha Schmidt" wrote:

Hi again!

Well, the first part of my "mission" (calling remoting objects from a
webservice) is solved. But there's another part: Calling
this C#-Webservice from a java client.

Is this a difficult task? Or is this quite easy, like just a few lines
of source and using some of the packages from apache.org?
Has anybody done this before and will like to tell me about his/her
experiences?

Thanks in advance!
Sascha