On Fri, 21 Jul 2000 11:42:55 +0100, Humphrey Sheil
<[EMAIL PROTECTED]> wrote:
><MY QUESTION>
>Now this raises a point with regard to what EJBs can and cannot do:
>
>I should not be able to do file i/o, use classloaders, fire off worker
>threads etc. within an EJB (see EJB 1.1 spec: 18.1.2 for more details) but
>I can. My experience indicates that vendors don't check for these spec.
>violations at ejb compilation time or runtime.
The spec mandates minimum requirements, which is to disallow certain
things. Contrary to intuitive thinking, allowing these operations are
actually BEYOND what the spec says. But, to make portable beans you
should not rely on the EJB container to be able to do this.
Do you see what I mean? Think backwards and it will be correct.
>So to ask this question in a more general way, is it correct that if I know
>I will be doing something which EJBs should not be allowed to do, to pull
>that functionality into a non-EJB helper class? Will this approach satisfy
>the specification requirements in this area for the foreseeable future
>(1.1/2.0 and beyond)?
Correct.
>Do vendors plan to start checking these restrictions into their products any
>time soon?
<vendor>jBoss (see jboss.org) already does this, although we have the
option to turn these restrictions off</vendor>. In an ASP environment
one would not desire the option to turn this off however, as it allows
beans to crash the entire environment at will.
> If not, is there a reason?
Laziness is a likely reason. Most will hide this behind statements such
as "our customers want this!". "Is it a bug or feature?" kind of thing.
Not that, in accordance with the above statement, it *is* a
spec-compliant option to *skip* this.
> Do you have client feedback which
>says "no way - we're breaking the spec. right now thank you very much
>because we have to" or is it simply low priority?
It seems to be the case that the server administrator and bean developer
still are too a large extent the same individual, in which case it is
likely that this requirement is of a low priority. As soon as the
different roles, as defined in the EJB specification, are taken on by
several different indiviuals with different requirements, this will most
likely change so that not checking for these restrictions is considered
a "bug".
Makes sense?
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
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".
