> ..
> Therefore, portable enterprise beans must assume that the container
supports
> the exact permissions set described in the EJB spec.
>
> Vlada
>
> PS: Note that there is no security permission JDK to disallow an
enterprise bean to
> start a new thread. Therefore, we currently do not require that an EJB
container be capable
> of enforcing the rule that an enterprise bean must not start a new thread.
We are looking
> into a solution that would allow the container to enforce this rule.
>
My experience is that if you implement the EJB security permissions as per
the EJB spec, and try to create a new thread in an EJB, your bean will get
an AccessControlException (java.lang.RuntimePermission modifyThreadGroup).
===========================================================================
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".
