Richard,
So, this means your EJB bean should not use any 3rd party Java classes
because you can't guarantee they abide by the restrictions? 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?
-Ron
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Öberg
> Sent: Tuesday, October 26, 1999 10:46 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> Hi!
>
> Steve Roth wrote:
> > Do the standard EJB restrictions (no thread activity, no IO)
> apply also to
> > non-EJB classes used by the EJB?
>
> Yes.
>
> > 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?
>
> Yes. The important thing is that they have the same classloader. If you
> package U outside of the EJB-jar, and instantiate it outside of the bean
> (such as a RMI-object), then U does not need to abide to these
> restrictions.
>
> /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".
>
>
===========================================================================
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".
