Receive shape of type System.XmlDocument

[Doug Griffin]

I wish to have the receive shape that activates my orchestration be of type
System.Xml.XmlDocument so that I can receive simular messages with slightly
different schema structures and re-cast them inside my orchestration to a
specific schema.

No problem building and deploying but am encountering difficulty when
messages are delivered to my process. The initializing message shape raises
this exception "Ilegal characters in path". I am certian that my message is
valid xml, and the error message implies that for some reason BT is trying to
invoke the load method of System.Xml.Document (doesn't the complaint about
path imply that it is trying to go to a uri to get the message?).

I get the same error whether i use passthru or xmlReceive pipeline.

Any advise would be greatly appreciated.

[Ronbo]

That is a most curious error.

What kind of transport are you using to deliver the message to your process?
If its via http, it could be something IIS is doing.

[Ronbo]

I forgot to subscribe to thread replies, so this message is a placeholder to
do that.

Anyway, tell me what kind of transport you're using, maybe that'll narrow it
down.

[Doug Griffin]

Hi Ronbo.

I probably should have mentioned that i have published my orchestration as a
web service so it is going through IIS (solicit/resoponse). I thought it
might be the way i was constructing my message in my consumer (also BT
orchestration), but the message is making it past IIS into orchestration
(fails on initializing message receive shape) and when i save it out from
suspended i can see it is well formed xml.

Also tried a HTTP 2 way port with identical results.

[Ronbo]

Hi Doug

Though the error is surfacing at the activate on the orchestration, I'm
still suspicious that its doing so because IIS is passing directly to the BT
extension, and if that barfs the error bubbles up to BT so it reports it as
the first artifact in the chain. That's a theory anyway.

To test this how about taking IIS out of the equation - set up a file drop
location , drop the XML in and see if it dies or not. If it doesn't then we
know its specific to IIS or the adapter - its the transport. If it does die,
then we know it isn't the transport method.

That's one nice thing about diagnosing stuff in BizTalk, things like
transport and format are all well encapsulated, so its not hard to construct
tests that let you narrow down the problem area. That's my usual approach
(well, after hitting a search engine and seeing if somebody else already
figured it out, lol).

Like I said, a most curious error, I love the interesting ones like this.

[news.microsoft.com]

Hi,

Maybe you can also provide the generated WSDL of the webservice endpoint.

It BTS 2009 is in use, it might be an option to give WCF-BasicHttp a try.

Thanks, regards

Joerg Fischer

"Ronbo" <Ro...@discussions.microsoft.com> schrieb im Newsbeitrag
news:402DE9D2-9147-44E2...@microsoft.com...