Fallback from VelocityViewResolver to JstViewResolver

[piks]

Hi,
I have started to migrate my app from jsp 2.0 to velocity. I want to be able to first resolve a velocity template, and if that fails load the corresponding jsp page. (/WEB-INF/velocity/start.vm -> doesn't exist -> try /WEB-INF/jsp/start.jsp).

I've tried to subclass UrlBasedViewResolver for the jstl view, implementing the ordered interface (to load it last), and VelocityViewResolver, implementing the Ordered intererface, and returning null when catching any exceptions in loadView(). However, the VelocityViewResolver still crashes when it doesn't find the view instead of delegating to the next resolver in the chain. (Seems like the exception never is caught.)

I don't want to use ResourceBundleViewResolver, since I just have to many views.

Any suggestions?

Thanks, Pontus

[jbetancourt]

I have a similar desire. I would like to use both Velocity and JSP pages. Velocity for simple output and JSP for forms and stuff.

Tried JstView resolver the velocity resolver but to no avail.