The first thing realize is that you cannot call Runtime.exec() without spawning threads to read the various IO channels. This is a known bug/feature of the JVM.
Thus, on the surface of it, the answer is no. However, I believe there are other considerations that would make this an undesirable design. Security being one of them! On the other hand, if you are stuck with having to exec() something, I would try to place that into a "service" that you access via one of the standard EJB methodologies. HTH, tim. > I am resending the message as I the email that I sent earlier > bounced back. I apologize for any inconvenience. > > ==========================Forwarded message========================== > > > Hi, > I have implemented a stateless session bean that calls a helper > class. I am spawn a process from a method in the helper class using > runtime.exec(). > Given that spawning threads is not allowed in the EJB server environment. > Is spawning processes okay? Is it not equivalent to spawning threads > which are nothing but light weight processes? > I need answers quite urgently. If anybody has experience in this > pls do let me know. Thanks. > > Venki > > ----- End forwarded message ----- > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
