Last week I was working with a colleague on a scenario in the Itinerary. In this scenario we are using an Orchestration. To use this Orchestration in the Itinerary we had to add the Orchestration to the ESB.Config,
so it can be selected in the Itinerary:
(note: it is not necessary that this Orchestration is deployed, it is not validating)
After exporting the model, the Itinerary contains the next line:
I still can’t think of a reason why this Orchestration should be added to the ESB.Config, because it can be resolved dynamically like the send ports from an application. Now all the developers must change their ESB.Config, and also the production version must be changed (the full name is not stored in the Itinerary, just a Guid or just a string as you wish). Why not store the full assembly name in the Itinerary?
Do you know the answer? Will this be a feature for the next release?
