Hi, Just adding my 2 cents. Go with Duncan because: 1) He works for Oracle, so he _must_ know what he's saying :) 2) His approach works nice here in my job. Oracle's replication features work good. If you are a bad luck guy that doesn't have a DBA in your team (yeah, it is possible) you can try using a db link so your code doesn't need to make two database connections. Let Oracle handle the connection to the other database :)
HTH, Daniel Silva. On 7/14/05, David Whipple <[EMAIL PROTECTED]> wrote: > We use the cron approach as well. Using a simple mechanism and having > separate JVMs has proven very good for maintenance, etc. > > Dave > > > > > Larry Meadors > <[EMAIL PROTECTED] > ail.com> To > Struts Users Mailing List > 07/13/2005 11:49 <user@struts.apache.org>, Richard > PM Reyes <[EMAIL PROTECTED]> > cc > > Please respond to Subject > "Struts Users Re: [OT] Java as a Daemon > Mailing List" > <[EMAIL PROTECTED] > he.org> > > > > > > > > I would probably go the route of the .sh file. > > At the risk of starting a big flame war, cron is solid as a rock, and > all of the memory used by your app will be freed up when the JVM > exits. Why make it more complex by adding quartz or tomcat to the mix > if you do not have to. > > Simple is *almost* always better. > > Larry > > > On 7/13/05, Richard Reyes <[EMAIL PROTECTED]> wrote: > > Hello Guys, > > > > I need your suggestions. I have a task to create an application to > > sync records between 2 Oracle 10g database. Not the whole records of > > the database though, just the now and then transactional updates. > > Access to the db's would be both via web services. I think I have an > > option to do this like > > - a simple java application executed via .sh file > > - a java application running as a daemon on a unix box > > > > But I really am not sure which better path I should take. Any > > suggestions would be very much appreciated. > > > > Thanks > > Richard > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
