Comments on David Blevins' Blog: @ApplicationException is evil... sort of

Hi, you have a typo in the ejb-jar.xml:
2010-11-11T02:02:03.134-08:00
Hi,

you have a typo in the ejb-jar.xml: java.lang.RuntimeExceptions

should be RuntimeException.

And I have a question. Does it mean, that all subclasses of RuntimeException are considered as ApplicationException, or just RuntimeException itself? Thanks

2010-11-11T02:00:19.726-08:00

This comment has been removed by the author.

Would definitely be a welcome addition to the spec...

2010-08-26T02:01:36.056-07:00

Would definitely be a welcome addition to the specs!

Exception handling is to coarse grained and now the only solution is to use BMT to control the transaction.

2010-08-26T02:00:16.863-07:00

This comment has been removed by the author.

Having an ApplicationException on the bean side is...

2010-07-29T20:22:51.354-07:00

Having an ApplicationException on the bean side is a good idea, with it, there will be a fine-grained policy for exception handlering. Actually, I just got an issue reported by the customer, they said that the MDB instance is destoryed sometimes, and finally find it is caused by a runtime exception. But from another side, I guess that, for the developers, it might be hard for them to predict which runtime exception will be thrown from the method body, as from the desgin perspective of runtime exception, it is not expected while writing the codes.

Very nice idea. Definitely a plus if added

2010-07-17T06:03:34.877-07:00

Very nice idea. Definitely a plus if added