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
