Hi Steve
It applies to the thread used by the EJB container. So any classes methods
called by that thread will be restricted. You need to pass an asyncronous
request to a thread outside the EJB container to access this functionality.
There was a discussion on one of the EJB lists about the use of doPriviliged()
at container level to relax this restriction for 'system' code.
Joel Crisp, Senior Java Architect, SUN PS Java Center UK
Steve Roth wrote:
>
> Do the standard EJB restrictions (no thread activity, no IO) apply also to
> non-EJB classes used by the EJB?
>
> For example, suppose I have EJBBean A (either BMP or CMP) and util class U.
>
> Inside A's methods on the remote & home interfaces, A instantiates a U and
> calls methods on it.
>
> Must the U methods (executed in the EJBserver JVM) also abide by the EJB
> restrictions, or are they free of these constraints?
>
> Thanks
> -Steve Roth, [EMAIL PROTECTED]
>
> ===========================================================================
> 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".
