Re: [Springframework-developer] RE: Using multiple view resolvers

[Colin S. <col...@ex...>]

I added a an enhancement request in Jira a while ago
  http://opensource.atlassian.com/projects/spring/browse/SPR-236
which is about this issue.

I see two possible solutions. One is a general view resolver that itself 
contains a list of other view resolvers, and delegates approproately 
based on a regex. The other way to approach it is to just put the regex 
code itself in either UrlBasedViewResolver or 
InternalResourceViewResolver, where the resolver would just skip its own 
execution if the regex didn't match, and you would just chain one or 
more resolvers normally, but now InternalResourceViewResolver could be 
something other than the last one.

I should be able to get this in for 1.2...

Colin

Alessandro Di Bella wrote:

>Hi Jürgen 
>I understand now. A solution I thought of is to create my own ViewResolver 
>that acts as a proxy and depending on some criteria it will delegate to the 
>appropriate ViewResolver. I still have a problem though, if I have more than 
>a bean that implements org.springframework.web.servlet.ViewResolver, how do I 
>tell the servlet which one to use?
>
>Thanks
>
>Alessandro
>
>
>jürgen höller [werk3AT] wrote:
>
>  
>
>>Hi Alessandro,
>>
>>Spring's view names are supposed to be global for the scope of a
>>DispatcherServlet. Hence, all controllers in the same dispatcher will
>>share a single view namespace. There is no support for having "local" view
>>names that just apply to a specific controller, with different controllers
>>returning the same view names but referring to different views.
>>
>>Essentially, Spring does not use the same view name semantics as WebWork
>>here, where view names are usually local: for example, "success" or
>>"form". View names in Spring are rather meant to refer to shared physical
>>resources, thus being global (for the scope of a dispatcher): for example,
>>"orderForm" or "orderList".
>>
>>If you still want to use local-style view names, you could collect some of
>>your controllers into a separate DispatcherServlet context, having their
>>own view namespace there. Or you could use controller-specific prefixes
>>for view names.
>>
>>Juergen
>>
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...]On Behalf
>>Of Alessandro Di Bella
>>Sent: Tuesday, November 09, 2004 6:29 PM
>>To: spr...@li...
>>Subject: [Springframework-developer] Using multiple view resolvers
>>
>>
>><posted & mailed>
>>
>>Hi,
>>
>>I apologize for posting this in the developer list but i did not get any
>>answer in the users one and I'm stuck.
>>
>>
>>I'm trying to put together a web app and I'm trying to understand how to
>>use the view resolver. I should to get the XmlViewResolver to work but i
>>don't understand how I can associate a specific resolver with a
>>controller. I'll explain better. I have a MultiActionController e several
>>SimpleFormController(s) that are mapped to different paths.
>>I would like to be able to say that if the request is handled by the
>>MultiActionController, the views sholuld be resolved by the
>>XmlViewResolver while if the request if handled by SimpleFormController
>>foo, the views should be resolved by the resolver bar.
>>
>>Is this possible?
>>
>>Thanks
>>
>>Alessandro
>>    
>>