The .NET side is going to have to parse the XML either way. Web
servies only every pass text around, they can't pass around objects.
So you're not passing a CF XML document object with type="xml", you're
passing a nested XML document. The XML document will be part of the
SOAP document (with type="xml"), rather than an XML-escaped string in
the SOAP document (with type="string"). So using type="xml" will only
save you the XML-unescaping on the receiving end, not parsing the XML.
Here's a completely contrived example that has little basis in
reality, but which will illustrate the point:
passing with type="xml":
<soap>
<var name="myDoc">
<rootOfDoc>
<childInDoc />
</rootOfDoc>
</var>
</soap>
passing type="string":
<soap>
<var name="myDoc">
<rootOfDoc><childInDoc /></rootOfDoc>
</var>
</soap>
cheers,
barneyb
On 8/4/05, Dharmendar Kumar <[EMAIL PROTECTED]> wrote:
> Yes, I can return "string" - pass XML string and it works in .Net
>
> But I wanted to pass a XML document object - so the receiver doesnt have to
> parse thro' the xml.
>
> But you made an interesteing point - that .net may not support 'document'
> type - i will investigate if that indeed is the case....
>
> meanwhile, any other insight is appreciated.
>
> Thanks
> DK
>
--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com/
Got Gmail? I have 50 invites.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:213783
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
