[jboss-dev-forums] [Design of JBoss jBPM] - Re: refactor code out of ExecuteJobThread in Command

managing threads on the other side of a session facade is not a good thing. if you look at the job executor as a component, you could think of commands like start-new-thread and stop-thread or set-nbr-of-thread. but still the threads would be managed by the component, not the actual command. hmmm... this reasoning is not really (thread?)-safe :-) probably it depends on what you want to do. but i don't see yet a use case in which you want to manage the job executor. i would think it is always a deployment kind of thing. 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. just thinking out loud here. i didn't really see yet where you want to take it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051370#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...