Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Schema Namespaces confusing Map Transform configuration?
- This topic has 0 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
March 30, 2010 at 5:49 PM #24487
Hi,
I have two schemas, one called Parent.xsd and LineItem.xsd.
They both have the namespace a.b.c. Parent is defined as the root node in Parent.xsd and LineItem is defined as the root node in LineItem.xsd. Parent.xsd includes (not imports) LineItem.xsd schema as the Parent can have a collection of LineItem nodes so LineItem was defined as a data structure type so it could be reused in Parent.xsd.
Form is set to Qualified on the LineItem element in Parent as it has distinguished fields and the xpath created by BizTalk has the namespace in it.
Example of generated Parent.xsd.
<nso:Parent xmlsn:nso=”a.b.c”>
<Name></Name>
<LineItems>
<nso:LineItem> (Schema Propety:Form = Qualified)
….Line Item nodes
</nso:LineItem>
</LineItems>
</nso:Parent>
In my orchestration, i debatch a LineItem from the Parent message and store it in it’s own message. I then have to feed the Parent message (need the non line item data for input) and 1 instance of the LineItem to be sent to a third message was is then sent to a endpoint for processing. I can’t send in the collection of line items.
So what happens when I created the map that accepted the Parent Message and 1 LineItem message the Message Part Type was set correctly when the map was initially created.
Initial configuration on Transform Shape
Variable Name Message Part Type
msgParent MyProject.Schemas.Parent
msg1LineItem MyProject.Schemas.LineItem
Save and compiled the orchestration, everything compiled correctly. Went back into the orchestration and right clicked on the transform shape and selected configure. Got a pop up indicating says that the signature of the map file has changed, some arguments that you specify may not be valid.
Took a look at the expected message part types on the transform shape for the map and where it was expecting MyProject.Schemas.LineItem it is now asking for MyProject.Schemas.Parent.
Variable Name Message Part Type
msgParent MyProject.Schemas.Parent
msg1LineItem MyProject.Schemas.Parent (Map now thinks that we are asking for a Parent message type)
I did some digging around the error signature of the map file has changed, some arguments that you specify may not be valid and found a few links, most of them ask you to make sure that you have unique namespaces and/or unique root node name which I do have unique root node names.
Anyone have any ides? Run into this before? I am using BizTalk 2009
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.