On 27 Sep 00, at 10:49, Rickard Oberg wrote:
> Hi!
>
> > I have noticed that jBoss doesn't log application exceptions, but send
> > them to client. I some places such logging is commented out and marked
> > as "debug". I think it would be more convenient to jBoss users
> > (at least for me and my colleagues) to see the full stack trace on
> > server in addition to the short exception message only that is
> > available on client (since the application exception is wrapped by
> > some RemoteException).
> > Any other opinions?
>
> App exceptions should not be logged on server. It should be possible to
> propagate them to client without loosing too much information.
>
> OTOH, it should perhaps be possible to have a "debug" flag in container that
> allows app exceptions to be printed there as "Warning". But for production
> IMHO this should be turned off since many app exceptions are just "normal
> operation".
+1. Application exceptions should not be logged in a production
system.
On the other hand, system exceptions should always be logged.
They indicate abnormal operation, and anyway the specification
requires that they be logged.
If there is a specific logging requirement for your application, you
probably want to use a portable solution anyway--such as an
actual logging or management framework (JMX, perhaps?). jBoss-
specific behavior with regard to application exceptions would not be
portable, and so is probably not the right choice for your application.
-Dan
>
> Makes sense?
>
> /Rickard
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
