Carol,
I think these have been answered to a degree, but I'll chime in for
posterity:
Carol writes:
> -----Original Message-----
> 1) What is the best recommended way (within the standards) to
> do logging for an EJB application? I want to have 1 (singleton) object
> responsible
> for logging to a file.
>
An RMI or CORBA singleton is adequate for this. I use a CORBA event service
with a logging helper class wrapped around it. This way we can have a simple
API for loggers to send log messages, and many possible log writers
listening to the log channel. You could do the same with JMS...
> 2) What is the best and most performant way to have 1 (singleton) object
> load and cache read
> only data and make it available to other EJB's.
>
Given a distributed environment, you could again use an RMI or CORBA
singleton for this purpose. In GemStone/J we have the added possibility to
cache in PCA which acts as sort of a virtual distributed singleton. But
maybe Sun can't use their good partner's server ;-)
> 3) Should referential integrity be turned on in the Database when using
> Entity Beans? Could
> this cause problems if a bean which references other entities gets deleted
> ?
>
Some DBA guy and answer this. I don't see what the problem is, except that
the container may have to be sensitive to RI in terms of the order of SQL
statements that are fired.
Regards,
-Chris.
> ==========================================================================
> =
> 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".
