Re: [Springframework-developer] RE: [Springframework-user] chain ViewResolvers?

[Seth L. <se...@eh...>]

>>That said, we could also stick to a single "viewResolver" bean and offer a
>>"ChainedViewResolver" adapter that takes a List of further ViewResolvers
>>that it delegates to.
> 
> Hmmm, the ChainedViewResolver would be inconsistent with the possibility of
> having multiple UrlHandlerMappings, which are NOT contained by a
> ChainedHandlerMapping or something like that... Once you get used to the way
> beans are defined in the WebApplicationContext it's really intuitive, so we
> shouldn't go and introduce concepts like this IMO.
> 
> Also, I don't like workarounds or inconsistencies to be able to include
> something that might otherwise result in a non-backward-compability... So
> AFAIC the ChainedViewResolver is a no-go... This would mean we can't add the
> multiple viewresolvers... But I don't like that either!

Just catching up on the discussion (the problem of living so far away is 
that my day is your night :).

I'm curious why you think a ChainedViewResolver would be inconsistent. 
I view it as a new feature, not as breaking a pattern.  It certainly 
seems the most simple (maintains 1 viewresolver for the servlet, allows 
for explicit ordering by definition of the chain, doesn't change any 
semantics on return variables, etc).  Also, we can always add 
ChainedHandlerMapping.

I'm not arguing, and I'm very pleased to see multiple viewresolvers now 
able to be specified (although still curious as to how to order, but 
will check that out shortly).  Just wondering what the thought process 
is from those who know Spring better than I. :)

Thanks!
Seth