> Option 1: Just make a logging service, as you would in any other app.
> Use right away from your beans, but be sure that you got the classloader
> thing covered.
> Option 2: Use JMS. Send messages to some queue which has a receiver that
> performs the actual logging to the file.
> Option 3: Check if the server has builtin support for such logs (it
> should if it costs a lot of money..)
>
> 2 (or 3) is preferred if possible IMHO.
>
Rickard,
I may be a little dense this morning.
Option 1: Is the logging service part of a EJB bean or a class it accesses?
How can it do i/o under the EJB restrictions?
Option 2: I'm assuming the receiver is another jvm outside the EJB server?
Wow, messy design.
Option 3: Then I loose portability by coding for a specific vendor's EJB
server, right?
Goodness. Didn't the EJB spec writers expect this type of need? Are we all
going to do it differently?
-Ron
===========================================================================
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".
