You would need some interception of the Quartz event to set up the Seam contexts (Lifecycle.beginCall(), Lifecycle.endCall()). I don't know enough about Quartz to tell you exactly how to do it.
Thanks Gavin but I think that might require a slightly better understanding that I have.
Taking the broader problem, running repeated actions from antoher thread and still having access to the seam beans . Can anyone suggest something please?
I have tried Component.getInstance("testBean") for example but I get
java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1534) at org.jboss.seam.Component.getInstance(Component.java:1584) at org.jboss.seam.Component.getInstance(Component.java:1567) at org.jboss.seam.Component.getInstance(Component.java:1561) at halvor.schedulers.db.PendingOrderQuartzTarget.execute(PendingOrderQuartzTarget.java:11) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
I am assuming I need to configure something with this approach but do not know where to start.
Any other approach suggestions are welcome; i am not tied to quartz in any way.
Have you tried using Seam 1.1 asynchronous methods?