At the moment I have a simple Application that creates a number of Threads that do some long and complicated Processes on a number of machines.
So the question is: Should the Thread be a Transactioned Stateful Session Bean - so it doesnt not get serialized during process? Or just a stateless Bean, which is given a bunch of parameters for the process at hand? At the moment the Threads have a instance variable which when called gives the state of the application at the present time - (eg: doing such and such, doing this that and the other). I want the client to be able to check up on the state of the machine when nesscary - would it be best to say: Every machine has a corresponding stateful bean for its processes or every thread becomes a stateless session for its processes? I can even see that an Entity bean may be useful becuase i would like the logs to be written to a database. Help! Cheers! [ August 16, 2004: Message edited by: Tom Hill ]