BizTalk Server Orchestration - Subscription changes depending on message .NET class

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > November 2004 > Subscription changes depending on message .NET class





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Subscription changes depending on message .NET class
Vasily

2004-11-18, 2:47 am

I have the orchestration that uses receive port with message type of my .net
class Document (class is XML-serializable) and send port of the same message
type. The orchestration subscription looks like:
ReceivePortID = {...guid...}
MessageType = http://mcdsoft.ru/Document#document

When I send XML (serialized from Document .net class object) to the
orchestration using FILE adapter and XMLreceive pipeline - it works OK.

But ones I add new message to the orchestration with type of RawString (from
send e-mail sample) and redeploy the orchestration - the subscriptions looks
like:
ReceivePortID = {...guid...}
MessageType = Document

and therefore the orchestration cannot retrieve message causing error about
missing subscription.
It seems that when I try to use non-XML serializable .net class as message
type - it changes subscription of orchestration receive port.
How can I fix this?


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com