> How about using the CORBA event service? It has the concept
> of a "channel"
> which is natural for logging.
>
Interesting idea. But how different, or more efficient is this than
a JMS (hub and spoke design) is Corba event service?
I'm sure we've written debug logging into our commercial services that
when turned up to 100% write many Mb/minute of log files. Efficiency
is key, else you're buying Sun boxes to write logs and not deliver corba/DB
services.
I'm not sure why there's very little talk about the lack of error eventing,
logging and debugging facility from their deployed and commercial
quality beans.
Is everyone taking the design approach of throwing SQLException wrapped
in chained domain exceptions back to the GUI client? What about the
system operations staff. How are they to find out that a DB is out of
connections etc?
Another approach, that the bean spec / container vendors could have
facilitated
is integral SNMP MIB support. Where the Bean may emitt traps on serious
errors. This seems to be a more inteligent approach than log files anyway.
But, there's only commercial libraries for SNMP, no container support or
javasoft reference APIs (yet?).
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".
