[
https://issues.apache.org/jira/browse/TREQ-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406717#comment-13406717
]
Nicolas Le Bas commented on TREQ-13:
------------------------------------
I'm having a hard time coming up with a elegant design that would keep the
current features (based on VelocityView) and at the same time still work
without Servlets. The reasons are multiple:
* VelocityView is a facade pattern that deals with several aspects that exist
separately in Tiles Request: it merges Request and Renderer into a single class.
* Many features of Velocity are based on tools, and many of those tools depend
on VelocityView and Servlets.
* The support for localization in Velocity is based on tools, too, and it is
incomplete. For instance Spring have worked around this problem by implementing
their own DateTool and NumberTool.
So we may end up with 2 velocity implementations, in which case I would like
deprecate the old one based on VelocityView.
> Velocity implementation that doesn't rely on servlets
> -----------------------------------------------------
>
> Key: TREQ-13
> URL: https://issues.apache.org/jira/browse/TREQ-13
> Project: Tiles Request
> Issue Type: Improvement
> Reporter: Nicolas Le Bas
>
> The current tiles-request-velocity relies on velocity-tool and servlets. We
> should be able to build an implementation based on VelocityEngine directly,
> dropping the requirement for a servlet container.
--
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
