BizTalk ESB 2.1 - Right message, wrong message type -
i have request/response itinerary made of orchestration extenders. works fine including message sent web service. in receive port there outbound map never gets fired. have tracked down fact message, although correct, has wrong message type context. infact has context of message few steps in itinerary. why , how can solve issue?
btw have tried changing context in pipeline component followed esb transform component no avail.
not particularly satisfactory solution in end took maps out of receive port. colleague had suggested best practice have layer of abstraction in fact relevant 'classic' biztalk.
the issue in particular case appears have 2 identical schemas different namespaces. reason being if external schema changed map internal in port without changing else. again useful classic biztalk negates changes orchestration not relevant esb.
Comments
Post a Comment