> There is an EJB FAQ entry on jGuru.com that covers logging.
>
> http://www.jguru.com/jguru/faq/view.jsp?EID=8993
>
Richard's EJB FAQ contribution offers EJB a few choices for useful debugging
and production quality bean implimentation that we used to have in Corba/RMI
architectures that did not require wire calls, additional VMs, or much much
more code and complexity.
I.E. the ubiquitous Singleton that must have been reinvented several 10k
times
because Java was lacking a commercial log/debug package; MyLogClass and it's
methods; writeLog(String aMsg),, etc that we have all writen and used for
all uses except EJB.
<ranting>
Now I need to use JMS??? The performance loss is what? 10x or 100x slower
than a Singleton with background writer thread to a local log file..
The Container should have offered a log object in the EJBObject or the
context
objects!!
My complaint (stamping feet, waving hands, red faced) is that just because
the Java API has still omitted a standardized logging facility why should
EJB
have just continued this serious omission?
... the emporer's a bit thread bare in the deployed environment debugging
and
logging department. IMHO.
:)))
</ranting>
Now my todo is to wrap my logging singleton in a Corba service. __Some__
EJB
app servers are also compitent Corba servers where a Corba service can be
resilient at the method and or the naming service layer. My opinion is that
JMS is too inefficient (eats too much CPU/VM) for high volumn debug logging.
Has anyone deployed a more efficient and resilient architecture than moving
logging to a group of purpose specific Corba logging services that are
resilient??
Thanks,
Curt
Curt Smith
Z-Tel
email: [EMAIL PROTECTED]
work: 404-237-1166 x182
FAX: 404-237-1167
===========================================================================
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".
