Hi everyone, I have a question related to the implementation of EDA messaging strategies in ServiceMix. How would you implement the following pattern in ServiceMix?
1) Some action happens within an application such that it needs to notify the ESB so that other systems are updated accordingly, so it casts an event onto the ESB. 2) The ESB transforms the data from the applications particular data model into a canonical data model and publishes the message in this common data format to a certain "topic" (I come from a TIBCO background, so we call this a "subject" in Rendezvous terms). 3) All applications interested in snatching this event subscribe to the topic they know beforehand. 4) The ESB transforms the message from the canonical data model to the destination's particular model and invokes the appropriate endpoint on the target application. This means that there is no service choreography (one service doesn't invoke another one), nor there is service orchestration (as we do not know beforehand what services should be invoked). How would you best implement this EDA behaviour in ServiceMix? What components would you use to: 1) do the transformation (servicemix-saxon?), 2) publish the message to the ESB on an agreed topic, 3) subscribe to the agreed topic, 4) do the reverse transformation? Thanks a lot for your help! All insights will be appreciated. Regards, Raul. -- View this message in context: http://www.nabble.com/ServiceMix---EDA-tp16291801s12049p16291801.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
