Investigate how to support more than 1 view resolved through the BeanNameViewResolver [SPR-5646]

[spring-projects-issues]

Alef Arendsen opened SPR-5646 and commented

As discussed in the blog entry (http://blog.springsource.com/2009/03/16/adding-an-atom-view-to-an-application-using-springs-rest-support/) you can now support more than 1 view by using the ContentNegotiatingViewResolver. Aas Dmitriy and Harald are asking, it's not clear right now how to support more than 1 view through the BeanNameViewResolver.

For more info on the issue, have a look at the comments by Dmitriy and Harald: http://blog.springsource.com/2009/03/16/adding-an-atom-view-to-an-application-using-springs-rest-support/#comments

---

Affects: 3.0 M2

3 votes, 2 watchers

[spring-projects-issues]

Alex Coles commented

There's are a couple threads on the forums discussing this issue:

http://forum.springsource.org/showthread.php?t=73102
http://forum.springsource.org/showthread.php?t=74600

A couple possible workarounds:

http://forum.springsource.org/showpost.php?p=249805&postcount=2
http://forum.springsource.org/showpost.php?p=250444&postcount=3

(if workaround #1 is correct, then this issue would appear to be invalid).

[spring-projects-issues]

Ryan Stewart commented

I've posted another theoretical solution in this thread:
http://forum.springsource.org/showthread.php?t=74600

The actual post:
http://forum.springsource.org/showpost.php?p=264050&postcount=9

In short, I don't think it's the responsibility of the ViewResolver to participate in the decision of how a View gets rendered. That should be strictly up to the View itself. I think the content negotiation should be done in the View and not in the ViewResolver.

[spring-projects-issues]

Sébastien Deleuze commented

Closing groups of outdated issues. Please reopen if still relevant.