jmx has a timer service, and jboss has a more sophisticated scheduler service mbean. Would one of those work? Can you implement the task controllers as mbeans also and view the progress through jmx?
david jencks On 2002.09.02 20:44:18 -0400 G.L. Grobe wrote: > Looking for anyone who has implemented a scheduler of any sort in their > J2EE apps? > > My application is layed out on JBoss 3.0.1 as ... > > Velocity pages -> Webwork Servlets -> EJB's > > Problem is I'm not sure where to put a scheduler in this mix. Some jobs > are triggered on demand from the user (no problem here). Other jobs that > are stored in the database (like cron tasks) need to be triggered, I'm > guessing by an external scheduling server. I'd then like the job progress > information from that external scheduler server to be viewed by the users > (which means communicate back to the JBoss server). > > In otherwords, I'd rather not have the complexities of an external app to > have to trigger and communicate back and forth to JBoss if I don't have > to ... but I don't see how to get around it since ejb's don't seem to be > a good place for this to happen. Be nice to keep it all in one package. > > I hope that was clear, any ideas/thoughts much appreciated. > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> > <META content="MSHTML 6.00.2719.2200" name=GENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=#ffffff> > <DIV><FONT face=Arial size=2>Looking for anyone who has implemented a > scheduler > of any sort in their J2EE apps?</FONT></DIV> > <DIV><FONT face=Arial size=2></FONT> </DIV> > <DIV><FONT face=Arial size=2>My application is layed out on JBoss 3.0.1 > as > ...</FONT></DIV> > <DIV> </DIV> > <DIV><FONT face=Arial size=2>Velocity pages -> Webwork Servlets -> > EJB's</FONT></DIV> > <DIV> </DIV> > <DIV><FONT face=Arial size=2>Problem is I'm not sure where to put a > scheduler in > this mix. Some jobs are triggered on demand from the user (no problem > here). > Other jobs that are stored in the database (like cron tasks) need to be > triggered, I'm guessing by an external scheduling server. I'd then like > the job > progress information from that external scheduler server to be viewed by > the > users (which means communicate back to the JBoss server).</FONT></DIV> > <DIV> </DIV> > <DIV><FONT face=Arial size=2>In otherwords, I'd rather not have the > complexities > of an external app to have to trigger and communicate back and forth to > JBoss if > I don't have to ... but I don't see how to get around it since ejb's > don't seem > to be a good place for this to happen. Be nice to keep it all in one > package.</FONT></DIV> > <DIV> </DIV> > <DIV><FONT face=Arial size=2>I hope that was clear, any ideas/thoughts > much > appreciated.</FONT></DIV></BODY></HTML> > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
