I ended up finding a solution, er, workaround, by moving the Quartz scheduler
into the Web layer instead of the EJB layer. In this regard, the threads
running in the servlet layer establish new remote connections to trigger the
EJB process. Slows down performance since it has to cross layers every time
the job is activated, but at least it works.
--
View this message in context:
http://www.nabble.com/Genimo-%2B-Quartz-%3D-No-Security-Context-tp16467530s134p16495642.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
