"Smith, Curt H." wrote:
> Interesting idea. But how different, or more efficient is this than
> a JMS (hub and spoke design) is Corba event service?
My thought as well. Hey, it's all ultimately sockets, right? :-)
> Is everyone taking the design approach of throwing SQLException wrapped
> in chained domain exceptions back to the GUI client?
You're not advocating this, right?
> What about the
> system operations staff. How are they to find out that a DB is out of
> connections etc?
Slightly off topic, but I've found that exceptions are an area that Java
tried really hard to get right, and didn't quite get there. I don't
think there's an easy answer. On the one hand, if the database is the
root cause of something failing, you want to show/expose/make available
the SQLException that caused it. On the other hand, if that
SQLException is buried inside some interface implementation, then one
would hope that the interface won't throw it.
A method on RemoteException or something similar that walked the
exception chain for you and returned whatever was on the bottom would be
most helpful.
> 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?).
Well, there's JMX which we're using
(http://java.sun.com/products/JavaManagement, if memory serves me).
Cheers,
Laird
===========================================================================
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".
