ansaurus

Question

Answer 1

+1 A:

JstlView implements ApplicationContextAware and ServletContextAware, so you should call setApplicationContext and setServletContext (and, probably, some other initializations) if you want to instantiate it manually.

But you can define a RedirectView in your views.properties, so you don't have to return a View object yourself:

someRedirectView.(class)=org.springframework.web.servlet.view.RedirectView
someRedirectView.url=/redirectHere

axtavt 2010-01-11 21:17:54

Thanks, it looks like an elegant solution to define redirect views in views.properties. But what if I need to build the redirect url at request time, something like "/redirectHere?id=" + id; Is it still possible to define it somehow in views.properties, and parameterize it?

adancu 2010-01-11 21:36:32

By default RedirectView exposes model attributes as URL parameters, so you can add your id to the model.

axtavt 2010-01-11 22:25:30

Answer 2

A:

The cause of your exception is that instances of JstlView need to be injected with certain things before they can be used, for example the current WebApplicationContext. Normally, this is transparent to you, because Spring instantiates and prepares JstlView for you. It's only when you do it yourself, that you see what's involved.

Now, you could call setApplicationContext on the JstlView that you instantiate, but you don't want your controllers getting involved in that sort of thing. You really want to keep Spring doing the work.

Now, since you're using views.properties, it follows that you're also using ResourceBundleViewResolver to resolve your views. The trick here is to realise that Spring can handle multiple view resolvers in the same context, it'll simply ask them one after the other, until one of them resolves the view name.

So my suggestion would be to add another resolver to your context, this time an InternalResourceViewResolver (this is actually the default resolver, but that default is suppressed when you specified your ResourceBundleViewResolver).

Now, when you return a view name that the ResourceBundleViewResolver can't resolve, the InternalResourceViewResolver will be consulted.

InternalResourceViewResolver just takes the view name as the actual JSP path (e.g. return /WEB-INF/page.jsp directly from your controller method). It also lets you use syntax like redirect:/path/to/my/url.

So yours other controllers can keep on returning view names as specified in views.properties, but now in addition you can return dynamically-assembled redirect:x/y/ view names, which will be translated by InternalResourceViewResolver into a RedirectView. No need to construct these views yourself.

One last point to note: the view resolvers are consulted in the order in which they appear in the beans file, and InternalResourceViewResolver must come last in that list.

skaffman 2010-01-12 13:19:54

Answer 3

A:

Not tested, but this should work

> projectView.url=redirect:/WEB-INF/jsp/project/view.jsp

Teja Kantamneni 2010-01-12 15:33:52

Answer 4

A:

This is a question. where should i place the view.properties in my proyect. i have troubles with ResourceBundleViewResolver because it's not finding the file and it´s throwing an exception.

*java.util.MissingResourceException: Can't find bundle for base name views, locale en_GB*

this is the mapping

<bean id="resourceBundleView" 
    class="org.springframework.web.servlet.view.ResourceBundleViewResolver">
    <property name="basename" value="views"/>
</bean>

Thank you.

OJVM 2010-04-16 19:37:55

ansaurus

tags:

views:

answers:

spring 2.5 jstl view error

related questions