[jira] Updated: (TAPESTRY-620) Expose the current IRequestCycle as an injectable service

["Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>]

     [ http://issues.apache.org/jira/browse/TAPESTRY-620?page=all ]

Howard M. Lewis Ship updated TAPESTRY-620:
------------------------------------------

    Summary: Expose the current IRequestCycle as an injectable service  (was: Place the current RequestCycle into the Infrastructure)

> Expose the current IRequestCycle as an injectable service
> ---------------------------------------------------------
>
>          Key: TAPESTRY-620
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-620
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 4.0
>     Reporter: Adam Greene
>     Assignee: Howard M. Lewis Ship
>     Priority: Minor
>  Attachments: Infrastructure_Cycle.patch
>
> Tapestry currently stores the WebRequest, WebResponse, and WebContext in RequestGlobals, which is then made available via the infrastrucuture: object provider and several other ways, but the RequestCycle is not and I have created a VelocityRenderer factory and configuration, and my goal is to make a simple service model that automatically renders Velocity and can be easily injected into pages, but I need access to the RequestCycle as part of the render process.  I have created a patch to that provides the RequestCycle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org