Rickard �berg wrote:
> A properly implemented server will not allow you to open streams during
> method invocations. This is enforced by applying the proper security
> policy.
Oh, pissy pissy pissy. :-( So if I have some business logic that due
to legacy reasons must tack on something to a log file I'm s*** out of
luck, is that it? :-( Rrrr.
Let's take that as a sample case. My first inclination would be to say,
OK, so I'll create a non-bean helper class that will open the log
stream, do the appending and return. But if it is called by an
enterprise bean, the security context will be propagated (yes?) such
that the helper class won't be able to open the log stream either.
Can you (or anyone else) comment on this? I'm feeling slow here.
Surely this is a common task that should not be prevented.
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".
