I think this is the best way, doesn't necessarily have to be JMS, but Armin get's style points for that ;)
m -----Original Message----- From: Armin Waibel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 2:32 PM To: OJB Users List Subject: Re: Change notification Hi Ryan, ----- Original Message ----- From: "Ryan Marsh" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Tuesday, August 27, 2002 11:01 PM Subject: Change notification > If I'd like change notification whenever an entity of a given type is > changed/stored in OJB what would be the best practice? > > I would like my application clients to be updated dynamically when a > WorkOrder object is changed (stored actually) by another instance. I > figure that I could fire off a JMS message and have the clients listen > to a JMS topic, but where would this message be fired from? I know two possible ways. Hope it would be best practice. Recommended way: Let WorkOrder implement the PersistenceBrokerAware Interface to get callbacks from the PB and let WorkOrder instance notify a JMS Producer. Or: Extend PersistenceBrokerImpl and override store-Method to check for WorkOrder instances. Change PB-class entry in OJB.properties HTH regards, Armin > > Thanks, > -ryan > -- > Humans are the unfortunate result of a local maximum in the > fitness landscape. > > www.ryanmarsh.com > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
