tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Greene (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Created: (TAPESTRY-620) Place the current RequestCycle into the Infrastructure
Date Fri, 02 Sep 2005 00:08:12 GMT
Place the current RequestCycle into the Infrastructure

         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
    Priority: Minor

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:
For more information on JIRA, see:

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

View raw message