Re: [Springframework-developer] MVC Exception Handling

[<jue...@we...>]

Rob,
=20
Indeed, the "mappedHandlers" feature is exaxtly meant for restricting =
the defined exception mappings of this resolver to the given set of =
handlers. The handler implementations, be it Controller or any =
convenience base class, do not have to be aware of it then. Such =
explicit support is much simpler than having to set up an AOP proxy just =
for this, I agree.
=20
Yes, the exception class names will be checked via isAssignableFrom. You =
can thus specify a base class and will catch all subclasses with it too. =
Regarding an example, you can have a look at Petclinic in M3, as soon as =
it is out. It forwards all DataAccessExceptions and =
TransactionExceptions to some custom MVC-managed error page.
=20
I agree that we need to document all those features: Actually, I'm quite =
keen on a feature freeze for 1.0 as soon as possible to facilitate this. =
I personally don't plan any further features; I know that Rod intends to =
do polish the AOP convenience classes a bit. So if we don't encounter =
any obstacles, RC1 should be out early December - the main difference to =
M3 being better docs and more examples rather than new features.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Rob Butler
Gesendet: Mo 24.11.2003 00:34
An: spr...@li...
Betreff: Re: [Springframework-developer] MVC Exception Handling



It sounds like Jurgen may have added the functionality I described =
above:

> A SimpleMappingExceptionResolver allows to map fully qualified =
exception
> class names (including base classes) to view names, restricting its
mappings
> to a certain list of handlers to be set as bean references to the
"mappedHandlers"
> property. Multiple resolver instances can thus define distinct =
mappings
for different
> handlers. A generic one without mapped handlers can be the last in the
ordered
> chain, providing fallback resolution.

So does "..including base classes.." mean that it will handle the =
subclassed
execeptions (instance of or isassignable) as I suggest above?

It sounds as if the capability to have a "default" and "over-ridding"
exception / view mappings has already been added.  : )

I think it would be great if some examples of how to set this up could =
be
created as well.  You guys are doing an awesome job of adding features /
functionality but I think the documentation is having a more difficult =
time
of keeping up.

Later
Rob



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer