James;
The spec is not really trying to save you from
yourself, but rather it is trying to save you from VM
and EJB Server vendors who implement their standards
diferently for some oddball reason, or simply bevcause
the underlying OS has some nutty properties.
By following the letter of the [law] spec., you
increase your chances of being able to port your bean
from one vendor to another, and these restrictions are
described that way in the spec. (ie. they are not
prohibited)
So to guarantee portability, have your beans read
properties from JNDI, not from property files directly
through java.io.
//Nicholas
--- James Cook <[EMAIL PROTECTED]> wrote:
> ----- Original Message -----
> From: Rickard �berg <[EMAIL PROTECTED]>
>
> > Me too, but more importantly I think I understand
> the intent behind
> > these restrictions (Server-side WORA, plain and
> simple). And I agree
> > 100% with them.
>
> I have a problem with the spec attempting to prevent
> users from themselves,
> and I think the file i/o issue is too restrictive.
> It sounds like you feel
> file i/o has no place in beans. Isn't there value in
> reading
> properties/config files? I can imagine that env
> settings can be too
> restrictive in some situations.
>
> jim
>
>
===========================================================================
> 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".
>
=====
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail � Free email you can access from anywhere!
http://mail.yahoo.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".
