- This topic has 1 reply, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
I’m trying to consume a web service from within an orchestration sending to it a custom type. I added the web reference, created the send port by selecting an existing Web Port Type and created a message based on one of the Web Message Types created when the send port was created. This is a Multi-part Type that has a message part called messageheader which I set using an object variable of the same type: EnterpriseEventRequestMessage.messageheader = ivcInterfaceEntity;
The assembly that holds the definition of the ivcInterfaceEntity is referenced by both the web service and the orchestration project. Both the messageheader and the ivcInterfaceEntity are instances of the same IvcInterfaceEntity (see at bottom).
The problem is that when the orchestration’s Send shape attempts to send the EnterpriseEventRequestMessage to the web service it is sending somethink like
<IvcInterfaceEntity xmlns=”http://tempuri.org“>
instead of <IvcInterfaceEntity xmlns=”http://www.mycorp.com/IvcInterfaceEntity“> which is what the web service is expecting.
The error I receive is:
Failed to serialize the message part “messageheader” into the type using namespace “http://tempuri.org/“.
[Serializable]
[
XmlType(Namespace = “http://www.mycorp.com/IvcInterfaceEntity”)]
public class IvcInterfaceEntity
{ …
-
I fixed it myself – by changing the web service namespace to match that of message coming in. re-referencing the Web Service to update the WSDL and it worked. I didn’t really want to do this as now all of my consumers need to deploy an updated agent with their apps because the namespace passed in the soap header no longer matches the new namespace of the web service … oh well!
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.