[
https://issues.apache.org/jira/browse/TREQ-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426610#comment-13426610
]
Nicolas Le Bas commented on TREQ-12:
------------------------------------
I'm not sure exactly why I implemented it this way. Possibly 2 reasons:
- l10n support
- calling renderer.isRenderable(path, request) and eventually pass control to
the next view resolver (URLBasedViewResolver never passes control: it only
checks viewNames before it even checks for redirects).
It may be worth testing it again... it should eventually extend
AbtractTemplateViewResolver, not UrlBasedViewResolver.
You can always setup an UrlBasedViewResolver on top of it, but perhaps
RendererViewResolver should implement Ordered.
> Spring integration
> ------------------
>
> Key: TREQ-12
> URL: https://issues.apache.org/jira/browse/TREQ-12
> Project: Tiles Request
> Issue Type: Improvement
> Reporter: Nicolas Le Bas
>
> Spring provides an integration with tiles-2. We need one for tiles-3, i.e.
> integration with the Request API.
> Tentative implementation here:
> https://github.com/nlebas/tiles-request/tree/tiles-spring
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
