ESB Toolkit How To Video #4: Dynamic Itinerary Resolution

re: ESB Toolkit How To Video #4: Dynamic Itinerary Resolution

olof — Thu, 18 Jun 2009 04:51:31 GMT

Hi,

There appears to be no sound with the video. Which sound codec did you use.

re: ESB Toolkit How To Video #4: Dynamic Itinerary Resolution

GrantSamuels — Fri, 26 Jun 2009 01:47:56 GMT

Hi Peter, been watching your video series on esb - it has been extremely helpful in making the jump from v1 of ESB.

I just have one clarification - when resolving itineraries from the pipeline using message content you can just use the normal fully qualified document type in the business rule, instead of Microsoft.Practices.Esb.ResolverProviderMessage.

In order to this you need to add the attribute recognizeMessageFormat to the BRI resolver connection like this: BRI:\\policy=MyIntinerary;useMsg=true;recognizeMessageFormat=true;

re: ESB Toolkit How To Video #4: Dynamic Itinerary Resolution

ryancrawcour — Sat, 25 Jul 2009 13:27:22 GMT

Hi Peter,

Excellent series of videos

I worked through this one step by step and I was wondering how you manage to workaround the problem InfoPath seems to have with xs:any.

You showed another prebuilt receive location, was this one using the acutal document type by any chance?

I can get it to work when i do that, but that's a hack because i then don't have this Generic Onramp which is meant to be our goal.

Any help on this would be greatly appreciated.

Thanks

re: ESB Toolkit How To Video #4: Dynamic Itinerary Resolution

ryancrawcour — Sun, 26 Jul 2009 08:16:31 GMT

@GrantSamuels

I tried your suggestion and I cannot seem to get this to work. If i take out the predicate that checks for the Level inside the document i can see the rule fires and always sets the "Composed" itinerary.

Put it back in without chaning the Document Type, with adding that new attribute and it fails!

I get an error about an Itinerary needs a parameter @name. Only assuming that the Fact that sets the name didn't fire.