Thank you Jeff. We now evaluate your solution for implementation. In last resort, we had thought about using JMS to send messages with the entity object whenevener an EJB writes to the database (in other words, using Flex Messaging). But your solution is more interesting as it would pass through the Data Management Service as we originally planned.
--- In [email protected], Jeff Vroom <[EMAIL PROTECTED]> wrote: > > Unfortunately there's no great way to do this automatically... DMS provides the DataServiceTransaction api which you can use to mirror any changes you make directly to the database but we do not have a hook to call these automatically in response to a database operation. > > The one approach I've heard of that works in some databases is to register a trigger in the database for that operation, then publish a JMS message in response to that trigger. Then in the LC DS process, you listen for that JMS message and use the DataServiceTransaction api to push that change out to the clients. > > Jeff > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of k.sigiscar > Sent: Wednesday, November 19, 2008 3:55 AM > To: [email protected] > Subject: [flexcoders] Can the Data Management Service detect database changes (not client changes) ? > > > Is it possible with LCDS to have the Data Management Service detect > database changes ? We already have LCDS configured with a custom Java > assembler. Any change commited on a client reflects to other clients > and in the database too. But we also have some backend processes > changing the database. In that case, is it possible to configure LCDS > to detect those changes to the database and push them to the clients ? >
