Ron Yust wrote:
> So, this means your EJB bean should not use any 3rd party Java classes
> because you can't guarantee they abide by the restrictions?
Yes, the restrictions seem to apply to the entire closure of the bean
methods' call graph. The implications of this are big, and it places
a lot of restrictions on what an EJB can use and do. The connector
architecture is being developed as one means to provide a container-
safe way to access outside resources. Other facilities will likely
be needed as well.
> What happens if you use a class that violates the spec? Does my
> EJB bean actually fail or can it just apologize to the container
> for being a bad bean?
That depends what it does. You might get lucky and nothing will
happen. If the class created a thread, and that thread crosses
over a container boundary that needs to access the thread context,
it could refuse access to a resource, or crash. If the class used
up some resources that the container needed to control, the
container could get upset.
I think the spec writers would call the results "undefined." In
some cases, an apology might be sufficient. In others, flowers and
a nice dinner might be required. ;-)
Paul
===========================================================================
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".
