> >Thats ok, but be very careful with sequence managers - i know > most of them > >are NOT happy with other apps doing inserts! see: > >http://db.apache.org/ojb/docu/guides/sequencemanager.html > > > > > yes I have not Other solution I can not convert Webapp 2 to use same Ojb > cache or OJB.
Thats fine. So which sequence manager are you using? > > >That depends on how often will app2 be updating/inserting data? > > > >If app2 only does it every few hours, i would put some code in > for app2 to > >make a request to app1 to do a broker.clearCache() Note that > app2 cant call > >broker.clearCache() directly as that would be an instance of OJB > under app2, > >not app1. > > > > > the application only does few hours to update/insert the base > If the application goes for long periods of time without updating/inserting data then i would suggest that you clear the cache after app2 does its work. I'm not sure if there's an easy way to do this, or even an easy way for webapps to talk to each other. Depending on how your app is written, i'd be inclined to write a method to clear the cache in App1, and trigger it using an http get from app2 (using somthing like http://jakarta.apache.org/commons/httpclient/). I've implemented similar things myself accross webapps on different servers. Hope that helps, Daniel. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
