Hey
Evan Ireland wrote:
> That is incorrect. "Portable" bean code may not use threads. This is the
> Bean Provider's responsibility. The Container is not required to prevent you
> from creating threads. As a Bean Provider you may not assume that such code
> will be portable, but it may work and be very useful in some EJB containers.
>From the EJB1.1 Draft 3 specification, page 277 (emphasis added):
"The following table defines the Java 2 security permissions that the
EJB Container *must* be able to grant
to the enterprise bean instances at runtime. The term �grant� means that
the Container must be able to
grant the permission, the term �deny� means that the Container should
deny the permission."
I.e. as a server vendor you *must* implement these restrictions.
The table does not contain 'grant
RuntimePermission("modifyThreadGroup")' which is necessary in order to
be able to create threads.
IMHO, a server that allows anything not explicitly granted in the table
can only be called "EJB based" and not "EJB compliant".
In light of this, can you expand your standpoint?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
