You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Adam Greene (JIRA)" <ta...@jakarta.apache.org> on 2005/09/02 02:08:12 UTC
[jira] Created: (TAPESTRY-620) Place the current RequestCycle into the Infrastructure
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:
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
[jira] Closed: (TAPESTRY-620) Expose the current IRequestCycle as an injectable service
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-620?page=all ]
Howard M. Lewis Ship closed TAPESTRY-620:
-----------------------------------------
Fix Version: 4.0
Resolution: Fixed
This was also an excellent chance to remove the IRequestCycle from several key interfaces, include IEngineService.getLink().
> 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
> Fix For: 4.0
> 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
[jira] Assigned: (TAPESTRY-620) Place the current RequestCycle into the Infrastructure
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-620?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-620:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> 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
> 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
[jira] Updated: (TAPESTRY-620) Place the current RequestCycle into the Infrastructure
Posted by "Adam Greene (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-620?page=all ]
Adam Greene updated TAPESTRY-620:
---------------------------------
Attachment: Infrastructure_Cycle.patch
> 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
> 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
[jira] Updated: (TAPESTRY-620) Expose the current IRequestCycle as an injectable service
Posted by "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