Thinking some more about it <:)/>
Jaws will throw an exception such as the Create or Finder Exceptions these
are to be seen as "BeanException", but they can be thrown by Jaws purely in
CMP.
I can't think of other plugins that would throw exceptions like that (that
are "bean" even though they are generated purely in jboss (no instance
call)...
maybe the Tx management ones where we come in and throw "concurent" on
Sessions for example (see TxInterceptorCMT on sessions)
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Wednesday, September 27, 2000 3:55 PM
> To: jBoss
> Subject: RE: [jBoss-User] Exception logging
>
>
> man we have to stop doing jboss-dev discussion on jboss-user but
> I will add
> to the fray...
>
> comments below...
>
> > One way to do this could be to define a new BeanException type
> > derived from java.lang.Exception that encapsulates the bean
>
> Yes the AppException encapsulating the exception Exception is what I was
> thinking of.
>
> > exception and change the invoke() and invokeHome() methods in
> > the interceptors to only throw BeanException. Such an exception
> > should probably have a boolean isAppException() method so that
> > it is easy for interceptors to determine what to do.
>
> or we could catch the beanException explicitely.
>
> > I would suggest that the containerinterceptors (last interceptor
> > in the chain just before the bean) encapsulate exceptions they
> > get from InvocationTargetExceptions in BeanException.
>
> yes
>
> > The container invoker can then unpack the BeanException and
> > return the right exception to the client.
>
> yes
>
> > Comments anyone ?
>
> nope... good for me... wanta take a crack at it?
>
> marc
>
> >
> >
> > Best Regards,
> >
> > Ole Husgaard.
> >
> >
> > marc fleury wrote:
> > >
> > > 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]
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
