WebServices & .NET (was EO & WebServices)
WebServices & .NET (was EO & WebServices)
- Subject: WebServices & .NET (was EO & WebServices)
- From: Jake MacMullin <email@hidden>
- Date: Tue, 27 Jan 2004 12:25:11 +1100
I've also experimented with using Direct2WebServices to interact with
Windows .NET desktop applications. While I've been able to get the
WebObjects side working - the .NET side trips up on the XML that is
returned by WebObjects every time - .NET doesn't seem to like the
'xsd:anyType' type that is returned by default from WebObjects.
I'm pretty sure this message to the axis-dev list describes the problem
(http://www.mail-archive.com/email@hidden/msg07057.html)
Also this thread in the soapbuilders Yahoo group seems to include a
post from a Microsoft employee acknowledging the problem.
(http://groups.yahoo.com/group/soapbuilders/message/7260)
It seems to suggest that using:
<id2 id='id2' soapenc:root='0' xsi:type='soapenc:Array'
soapenc:arrayType='xsd:anyType[0]'></id2>
in stead of
<id2 id='id2' soapenc:root='0' xsi:type='soapenc:Array'
soapenc:arrayType='xsd:anyType[0]'/>
will solve the problem.
This doesn't help me much though - how would I alter the XML that
WebObjects sends back using dir2WebServices?
Has anyone else tried to get WebObjects talking to .NET using
WebServices? Is there an easy way to get WebObjects to send the
response without using xsd:anyType?? Any success stories out there?
Regards,
Jake MacMullin
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.