Another option would be to let the ESB change the database itself. The service to change the data would be a service exposed on the bus, and it would send a notification when it updates a record in the database.
On Jan 19, 2008 10:21 PM, cchalmers <[EMAIL PROTECTED]> wrote: > > Hi, > > Together with a colleague I've just started a small project to build up > knowledge concerning EDA and have currently chosen ServiceMix as the > implementation tool. Bear with me as a lot of this is new new to me. > > The case we're trying to implement is a travel booking-system. Employees, > customers and airlines can be persisted after-which a customer can make a > booking etc. > > One of the things we want to prove is that when data changes in the > database > that an event is generated and action undertaken. For example if the > flight > data changes we want to send an sms to the passengers about the time > change. > > I read that others are connecting to databases via the spring jdbc > template. > The question is how an event as generated concerning the changed data? As > far as I see it there are two paths: > > 1. Continually polling the database from servicemix looking for changed > records which would have to have a last-modified data and then generating > an > event > 2. Working with triggers in the database which would somehow have to send > an > event to servicemix so that the sms can be sent. > > Is there a third (or more) option which I'm unaware of and is standard in > servicemix? > Perhaps I'm misunderstanding the EDA concept and how servicemix achieves > this? > > Plz let me know :-) > > thx > > /colin > > > > > -- > View this message in context: > http://www.nabble.com/ServiceMix---EDA---Database-tp14975289s12049p14975289.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
