I am planning on adapting the invocation layer to return the "Invocation" object and put anything you want in it.
This ties in with client side interceptors that can then retrieve anything you want on the client side (you can have a "exception interceptor"). I will do it soon, this is really relevant and generic enough marcf |-----Original Message----- |From: Anatoly Akkerman [mailto:[EMAIL PROTECTED]] |Sent: Wednesday, February 20, 2002 12:30 PM |To: marc fleury |Cc: Sacha Labourey; Jboss-Dev |Subject: RE: [JBoss-dev] Invoke returning an exception: how do you |expect it to be logged? | | | |Isn't this in a way related to making invocation results being |InvocationResult objects (something similar to Invocation but on a |return path). So you can stuff the resulting exception into it |and let an interceptor handle display of the exception? May be I am really |off here. | |------------------------------------------------------------------------- |Anatoly Akkerman |Computer Science Dept. |Courant Institute of Mathematical Sciences, NYU |715 Broadway, #719 Tel: 212 998-3493 |New York, NY 10003 Fax: 212 995-4123 |------------------------------------------------------------------------- | |On Wed, 20 Feb 2002, marc fleury wrote: | |> I think the example is well chosen, it has been annoying me for ever. |> |> Go ahead or log this as a feature request |> |> marcf |> |> |-----Original Message----- |> |From: [EMAIL PROTECTED] |> |[mailto:[EMAIL PROTECTED]]On Behalf Of Sacha |> |Labourey |> |Sent: Saturday, February 16, 2002 6:38 AM |> |To: Jboss-Dev |> |Subject: [JBoss-dev] Invoke returning an exception: how do you expect it |> |to be logged? |> | |> | |> |Hello, |> | |> |Currently, when a bean raised an exception, code in |Container.java:invoke |> |catch it, log it and wrap it in an MBeanException and re-throw it. When |> |logging it, it uses the ERROR logging-level. |> | |> |It has some annoying consequences. For example, each time an application |> |perform a findByPrimaryKey for example and the bean id does not |> |exist, a bit |> |stack trace is logged (and thus displayed at the prompt). But |in fact, this |> |is not a container issue but rather a standard bean's lifecycle issue. |> | |> |So, how do you expect exceptions to be managed by the container? |> | |> |What do you think if, in Container.java:invoke we would simply log |> |it at the |> |INFO level for example (or even DEBUG) and add more specific |behaviour in |> |Container sub-classes (i.e. if we want to manage finder exceptions |> |differently for example, we should deal with this at the |> |EntityContainer.java level instead of the more abstract Container.java |> |level) |> | |> |What do you think? |> | |> |Cheers, |> | |> | |> | Sacha |> | |> | |> |_______________________________________________ |> |Jboss-development mailing list |> |[EMAIL PROTECTED] |> |https://lists.sourceforge.net/lists/listinfo/jboss-development |> |> |> _______________________________________________ |> Jboss-development mailing list |> [EMAIL PROTECTED] |> https://lists.sourceforge.net/lists/listinfo/jboss-development |> _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
