[jira] [Commented] (TILES-541) VelocityAttributeRenderer does not pass context attributes

["Nicolas Le Bas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TILES-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295316#comment-13295316 ] 

Nicolas Le Bas commented on TILES-541:
--------------------------------------

We'll be rewriting the VelocityAttributeRenderer for Tiles 3.1, in order to make it usable without servlets (see 
[TREQ-13|https://issues.apache.org/jira/browse/TREQ-13]. Using VelocityEngine instead of VelocityView may also help 
the integration with Spring.

I'm not sure I understand the details of the problem you describe, especially the issues you're referering to. A patch may not help that much, however I'm interested in a test case.
                
> VelocityAttributeRenderer does not pass context attributes
> ----------------------------------------------------------
>
>                 Key: TILES-541
>                 URL: https://issues.apache.org/jira/browse/TILES-541
>             Project: Tiles
>          Issue Type: Bug
>          Components: tiles-velocity
>    Affects Versions: 2.2.2
>            Reporter: Konrad Garus
>            Assignee: Nicolas Le Bas
>
> VelocityTilesRequestContextFactory creates VelocityTilesRequestContext which still holds the velocity Context passed from outside.
> However, VelocityAttributeRenderer ignores this VelocityTilesRequestContext completely and creates a new context with velocityView.createContext(request, response).
> As a result the context map that is passed to Tiles from outside is not passed along to Velocity. Among other things, it is causing issues with integration of Spring, Tiles and Velocity.

--
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