Hey
Ron Yust wrote:
> 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?
Geez, you're getting obsessed with this "part of" thing.. ;-) If it is a
part of your bean or not is not important. I will only say this one more
time: it is the classloader that is important.
> Option 2: I'm assuming the receiver is another jvm outside the EJB server?
> Wow, messy design.
Might be, might not be. That's the strength. You may want to begin with
having the JMS client in-VM, but then change so that all running servers
send messages to a central log service. If you do not use JMS, it will
get messy. Having asynchronous messaging also improves scalability. Yyou
do not want synchronous logging. Why wait while some stupid service is
writing to a file, since it doesn't affect what you're doing.
> Option 3: Then I loose portability by coding for a specific vendor's EJB
> server, right?
Yup. It's a tradeoff.
> Goodness. Didn't the EJB spec writers expect this type of need? Are we all
> going to do it differently?
Until the Connector API comes along, yes. When it does we're all gonna
do it differently until some clever fellow comes up with the idea to
reuse the logging service and use the Connector API to interface with
it. And *then* it'll be happy happy forever after.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
