Hey
Paul Hodgetts wrote:
> > > Are you saying that none of the restrictions (threads, I/O, etc.)
> > > have anything to do with the thread originating from the client's
> > > invocation of the bean method?
> >
> > Exactly.
>
> I'm not sure that I buy into this, but I need to go off and read up
> before I can express an informed opinion. I still think the thread
> context is significant when accessing resources like JDBC, JMS, and
> J2EE connectors. The class loader seems significant when accessing
> library classes. Perhaps *both* play a part in the restrictions?
Threads are important when determining if the *bean* should have access
to a *resource*, and the classloader is important when determining if
the *resource* should be granted *Permissions*. So, yes, both. But the
entire discussion so far has been on the restrictions on what a bean
and/or other classes can and cannot do as defined in the EJB
specification, and that is *entirely* based on *permissions*, i.e.
codesource, i.e. *classloader*. Clear?
If not, then please reread EJB1.1 specification, and the docs at the
URL's I sent. It's all in there if you look hard enough.
/R
--
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".
