I agree,
I was looking at this this morning and application and container exceptions
should be separated in an interceptor. We have a "LogInterceptor" that
could do this work. It means retooling the exception throwing as container
or application and work accordingly with the interceptor. For exampel I do
not want to see the "Jaws" exceptions logged all the time (i.e the "entity
exists" etc) but the applications ex are important. We can probably do this
work in the interceptor mentionned, but I need to think some more about
it... it is a bit "all over the map" right now in the exception throwing and
handling... streamlining required :)
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Oleg Nitz
> Sent: Wednesday, September 27, 2000 10:54 AM
> To: [EMAIL PROTECTED]
> Subject: [jBoss-User] Exception logging
>
>
> 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?
>
> Best regards,
> Oleg Nitz
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
