You could also use a stateless session bean to write log messages
to a database (not a file). The bean would need the TX_REQUIRES_NEW
attribute, so that it would be committed regardless of whether the
calling bean rolled back its txn (if that is the semantics you desire).
A fairly expensive way to do logging, admittedly. But workable
according to the current spec.
-eric
"Tye, Tim" wrote:
>
> The best way is to find a logging resource on the container. (WebLogic lets
> you use System.out for logging or anything else).
> Also, a RMI process could be created to receive the logging request and
> merge them all into a single log file.
> > -----Original Message-----
> > From: WHITESIDE, CHIP [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, December 14, 1999 9:40 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: FilePermissions
> >
> >
> > 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.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Brininstool, Allen [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, December 13, 1999 4:57 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: FilePermissions
> > >
> > >
> > > I am referencing an object which does file I/O in a Session
> > > bean. I have
> > > used the policytool to create an AllPermissions entry for all
> > > files in the
> > > directory which contains the needed files. I am adding this
> > > entry in the
> > > 'server.policy' file in the J2EE lib directory. I am getting
> > > java.security.AccessControlException on the needed files. The
> > > entry in the
> > > server.policy file looks like:
> > >
> > > grant codeBase "file:/d:/adv253e/*" {
> > > permission java.security.AllPermission;
> > > };
> > >
> > >
> > > The d:/adv253e directory contains all of the files in question.
> > >
> > > Any ideas?
> > >
> > > ==============================================================
> > > =============
> > > 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".
> >
> > ==============================================================
> > =============
> > 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".
===========================================================================
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".
