anonymous wrote :
| another aspect is that you can also turn it around. you could just use the
JobExecutorThread in the command in stead of the other way round.
Actually, I tried this. But it is not easy to leave out the Threading in the current
implementation.
Maybe a solution would also be, to push some code for the Job-Execution in another class
(or the ScheduleSession maybe?), so the JobEexecutorThread gets much easier and I can
build a Command using the same code.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051372#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...