Orchestration exposed as web service — XmlDocument Type

Hi all,

I have an orchestration that I am attempting to expose as a web service where the in and out message type are untyped XmlDocument objects.

I can build, deploy and run the publishing wizard and generate the web service and add a reference to the WS from a basic VS.NET 2003 windows application.

Two things I’m not seeing well is the ability to receive the outgoing message, and I’m also getting an error I wouldn’t expect.

Here’s the client call:
[code:1:526496f1db]Function ProcessSalesFeed(ByVal xmlSale As XmlDocument) as XmlDocument

Try

Dim wsBTS As New BTSServices.ProcessSale
Dim xmlOut As New Xml.XmlDocument

wsBTS.ProcessSale(xmlSale)

Catch ex As Exception
MsgBox(ex.Message)
End Try

End Function
[/code:1:526496f1db]

The call to wsBTS.ProcessSale reports that it does not produce as value as I need it to, and when I make the actual call, I catch the following exception in HAT:

[code:1:526496f1db]specified cast is not valid[/code:1:526496f1db]

Any ideas?? Has anybody else has any success with using untyped messages within an orchestration exposed as a web service?

-Rich