- This topic has 5 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
hi everybody,
i have the following problem:
i have two schemas (schema1 and schema2) without target namespaces and with the same root node name deployed in my biztalk database.
i set a simple orchestration that just gets a message (schema1) from a file drop and deliver it into another file drop location.
now i already know that this will cause a problem because there will be two schemas deployed with the same message type. so i created a custom receive pipeline and set its "Allow unrecognized messages" property to true. but this is not working as the in message is failing in the custom receive pipeline with a "routing failure" error !! (note that the error message says nothing about loading schema types !!) the message is not getting delivered to the orchestration.
now once i undeploy "schema2" everything works fine without changing any thing else. is there something missing here?
note: i even set the (XMLNORM.AllowUnrecognizedMessage) property to true for the message supposed to be sent via the send port. but that did not work either as the message is not being delivered to the orchestration in the first place.
please i need help with this issue.
-
If your message is getting a routing failure, it means the pipeline is working as intented: The message is getting through to the message box, but because there was a conflict and the disassembler wasn't able to figure out the message type, it doesn't promote the MessageType property into the message context, necessary for typed subscriptions from orchestrations to work.
-
thanks tomasr for your reply,
now i feel that i am in big trouble. the project that i am working at forces me (according to the client internal system) to have many messages with the same root node and with empty target namespaces (same message type). so how do i overcome this in my scenario?
-
If you don't want to introduce a routing orchestration that receives generic messages and then tries to figure out what each one means and routes them to the right orchestration (which might be costly in performance terms), then your best bet (and the best solution) would be to write a custom pipeline component and make it part of the receive pipeline.
That component will have to figure out a way to see the real type of message from the message contents and correctly promote the appropriate properties. Sure sounds like a good spot for a probing component (seach google for IProbeMessage for details and samples)
-
thanks tomasr again for your help,
so what i am trying to do now, is to create a custom pipeline (my first ever actually), and inside the pipeline i am trying to promote the MessageType property and set it explicitly to the message type that my orchestration expects. i am thinking that then the subscription will work and the message will be handed to the orchestration.
will that work? if yes do you have any guidliness/samples that i could use?
thanks a lot.
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.