an asynchronous solution is definitely a better solution but either ways, you have to call some web services at the end to notify the web app , no ?
Regards, Youssef On Wed, Jan 7, 2009 at 12:35 AM, Edward Dowgiallo <eddowgia...@gmail.com>wrote: > This is also highly inefficient. You are taking on all the additional > overhead of a web service call for no reason. > > Ed > > On Tue, Jan 6, 2009 at 5:31 PM, Youssef Mohammed < > youssef.moham...@gmail.com > > wrote: > > > you can also have your trigger call a java package where you can simply > > call > > a web service (SOAP or RESTful). > > > > > > Regards, Youssef > > > > > > On Wed, Jan 7, 2009 at 12:26 AM, Edward Dowgiallo <eddowgia...@gmail.com > > >wrote: > > > > > Support for what you want to do is actually a feature in Oracle 11g. > For > > > Oracle 10g, you want to look at the publish/subscribe support which is > > part > > > of advanced queueing. The documentation is available online at > > > http://otn.oracle.com. > > > > > > Ed > > > > > > On Tue, Jan 6, 2009 at 5:22 PM, Bill Davidson <bill...@gmail.com> > wrote: > > > > > > > Is it possible to set up a callback like situation so that a trigger > in > > > an > > > > Oracle 10g database can call a method in a currently running webapp > > > > that's running in Tomcat 6? > > > > > > > > My situation is that I want to cache some infrequently changed > database > > > > data in memory but when that data does change in the database, I want > > > > the web applications, running on multiple servers, to immediately > pick > > > > up the change. > > > > > > > > Right now, one idea I have for this is to have the database trigger > > > > create a file in a file system that's shared by the database server > and > > > > the application servers and have the web apps check for the existence > > > > of this file to know whether to update the cache. It feels ugly and > > > > means hitting a networked file system a lot but it seems like it > should > > > > work and it seems like it should not be as bad as hitting the > database > > > > constantly for something that doesn't change very often. > > > > > > > > I'd rather have the database send a message somehow to the web app > that > > > > it needs to update its cache of the data. Any suggestions? > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > > > > > > > >
