You might consider Jini/JavaSpaces to coordinate tasks based on data availability, esp. if it were possible to write an entry to a JavaSpace at the point of the data change.
Fred Loney Spirited Software, Inc. www.spiritedsw.com ----- Original Message ----- From: "Sunder Rajan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 19, 2002 10:25 AM Subject: J2EE Scheduling Architecture > Hi Everyone, > I have a general question on J2EE scheduling. We run an application > that processes financial reports. We need to automate the report > generation. The idea is , The user will schedule certain reports from a > web page. The reports will run based on whether certain data is > existent on a different domain. So lets say a user schedules Job A to > run as an automated report. Job A will and only run when certain data > is available in database X. So the current architecture is to store the > different jobs in a table B, a startup class in weblogic will check the > database X periodically(30 mins) to check and see if data is available > and update the job in table B(set data to true). A different startup > class will periodically check table B and see if data flag is true and > kick of a report by starting a new thread(A new thread is required > since the reports may run for 30-45 mins). Do you guys see any > pitfalls/drawbacks with this approach. Is there a better way of solving > this? > > Thanks, > Sunder > > ======================================================================== === > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
