Thank you Laird, but that's summarizing it a bit too much...
I fully understand the restrictions and can even appreciate some
of them, and if I'd have more time I would have written this piece
of our system as a CORBA service or something like that, but time is
the one thing we never seem to have.
Currently our appserver allows me to do these things, but who knows if
in the next release they start to enforce the spec more rigorously...
I understand that at that time I may have to rewrite this bean into
something
else. Until then it stays.... Doesn't XP preach that the right solution
is the simplest one until proven that it is no longer right? At this time
writing it as a bean breaking all kinds of EJB rules is the simplest
solution.
Oh, and by the way, we're not worried about portability since we don't want
to
donwgrade to any other appserver out there.
Frank
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Laird Nelson
Sent: Monday, January 24, 2000 2:48 PM
To: [EMAIL PROTECTED]
Subject: Re: File I/O; not the usual question
Rickard Öberg wrote:
> Nope. Read archives. This topic has been covered extensively.
Hmm; indeed it has. The most salient article IMHO is by Frank Sauer who
quite rightly IMHO says, essentially, to hell with *that*; what a
ridiculous restriction. :-)
> Yes, *unless* you use doPrivileged() at appropriate times. Then you're
> off the hook.
Right.
Cheers,
Laird
===========================================================================
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".
