You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/09/22 22:16:28 UTC
[jira] Commented: (TAPESTRY-639) Expose the ServletContext as service tapestry.globals.ServletContext
[ http://issues.apache.org/jira/browse/TAPESTRY-639?page=comments#action_12330230 ]
Howard M. Lewis Ship commented on TAPESTRY-639:
-----------------------------------------------
Though, in retrospect, there's not much you can do with a ServletContext you can't do with the WebContext, which was already available.
> Expose the ServletContext as service tapestry.globals.ServletContext
> --------------------------------------------------------------------
>
> Key: TAPESTRY-639
> URL: http://issues.apache.org/jira/browse/TAPESTRY-639
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Vjeran Marcinko
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> ServletContext is required sometimes inside pages/components, for eg. standard Spring integration is done using it's util class that requires it (http://issues.apache.org/jira/browse/TAPESTRY-538)
> and currently only HttpServletRequest and HttpServletResponse injection is available.
--
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