Hey
How many times do we have to go through this?! Argh... here we go again
anyway:
You *can* dump them to a file, but you need to make sure the following
things:
* Grant I/O permissions to the class doing the actul file writing (this
usually involves editing some policy file)
* Wrap all actions that require permissions in doPrivileged blocks.
The underlying reasons and issues regarding this have been discussed
extensively on this list not long ago. Either check your mailbox or the
archives (http://archives.java.sun.com) for details.
All of this is described and documented in the Security API. See the
following doc for details on the above:
http://java.sun.com/products/jdk/1.2/docs/guide/security/spec/security-spec.doc.html
/Rickard
"WHITESIDE, CHIP" wrote:
> I was planning to have an error routine to trap errors in the bean, and dump
> them out to a file. How are people handling errors? Can you access the
> Application Server log file and dump out log entries?
>
> -----Original Message-----
> From: Tye, Tim [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 14, 1999 10:21 AM
> To: [EMAIL PROTECTED]
> Subject: Re: FilePermissions
>
> According to EJB specification, file I/O is not supported is session or
> entity beans. It appears that the container you are using is enforcing this
> restriction. You need to move the file I/O outside of the EJB TP container.
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
