Spring is starting to appear to be the best choice. Thanks for the reference.
On 13 February 2015 at 08:04, Daniel Mikusa <dmik...@pivotal.io> wrote: > On Fri, Feb 13, 2015 at 9:49 AM, Kevin Hale Boyes <kcbo...@gmail.com> > wrote: > > > We already use Spring in the project so I'll have a look there. > > > > > http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle/#scheduling > > Dan > > > > Thanks > > > > On 13 February 2015 at 05:29, Daniel Mikusa <dmik...@pivotal.io> wrote: > > > > > On Thu, Feb 12, 2015 at 11:59 PM, Kevin Hale Boyes <kcbo...@gmail.com> > > > wrote: > > > > > > > I currently have an application running on weblogic that I'm moving > > over > > > to > > > > tomcat 8. > > > > One of the things the application does is run background jobs using > the > > > > commonj WorkManager. These jobs are managed by weblogic which seems > to > > > be > > > > the recommended practice. > > > > > > > > What is the best/recommended way to run background jobs in Tomcat 8? > > > > > > > > > > Personally I'd use Spring, which has a nice and simple way to schedule > > > tasks. I'd also be using Spring for other things though and I'm not > sure > > > I'd pull it in just for scheduled tasks. > > > > > > A quick google search came up with this library. > > > > > > http://commonj.myfoo.de/ > > > > > > Haven't personally used it though. > > > > > > I suppose another option would be to just use java.util.concurrent. > > > > > > Dan > > > > > > > > > > > > > > Thanks, > > > > Kevin > > > > > > > > > >
