Dan, I can't call this elegant, but I prefer it to passing dao's in the JobDataMap..
I use Spring with Tapestry, and the SpringAwareStatefulJob from Spring that makes it easy to access the Spring application context. So, I still need to look up things that I'm accustomed to having injected, but I usually look up a service in the Job, and Spring handles injecting the dependencies for that service. Jonathan On Tue, Mar 31, 2009 at 2:16 PM, Daniel Jones <d...@murieston.com> wrote: > > Is there a more elegant solution than this? If so please share! > > Cheers, > Dan > -- > View this message in context: > http://www.nabble.com/T5---Chenillekit-Quartz---Services-tp22787045p22805264.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Jonathan Barker ITStrategic
