Alain , As I understand, loading JNI code can be insecured for the container. All restrictions are in place for good health for container, so if you load something in another process/jvm (as loading from jndi or rmi) will not effect container. In the same way, goes for threads. But I mentioned on the list before and again, that container can provide a pool of threads to developers/ejb which one can borrow and put your asynch job(runnable object) on it. I am not saying that we will manage the lifecycle , it will still be managed by container. Punit ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com =========================================================================== 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".
