Hi!
Stephan Gruschke wrote:
> R�> No, this is done by the LogInterceptor.
> Ups ... ok. Aehm ... which logger method? debug? warning? exception?
Not sure. Now that I think of it application exceptions shouldn't be
logged in the normal case (nothing is really wrong with the server or
application). RuntimeExceptions should be logged as an exception. App
exceptions could be logged as debug info though.
> >> and wrap it into
> >> an RemoteException.
> Ok.
>
> R�> No, application exceptions should be thrown as-is. RuntimeExceptions
> R�> should be wrapped through (in a ServerException I think).
>
> >> Is that ok? Otherwise we would have to modify the
> >> method signature which is not an option.
>
> R�> This is only for create, right? I think we have no other option but to
> R�> change the signature of the PM interface to allow application
> R�> exceptions.
> Nope ... seems to be createEntity(), findEntity() and findEntities().
> This would result in extending those method to throw Exception ...
> which could be difficult for higher modules to check which exception
> occured (same problem again humm). Just extending these methods with
> InvocationTargetException would point out that the bean made something
> wrong.
Hmm... tricky one.. needs some thinking. Are you sure finder methods can
have application exceptions?
/Ricakrd
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
