You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/06/24 15:42:48 UTC
[jira] Updated: (TAPESTRY-982) improve WebRequestServicerFilter and
provide the service information
[ https://issues.apache.org/jira/browse/TAPESTRY-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-982:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.1.3
> improve WebRequestServicerFilter and provide the service information
> --------------------------------------------------------------------
>
> Key: TAPESTRY-982
> URL: https://issues.apache.org/jira/browse/TAPESTRY-982
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 4.1
> Reporter: Henri Dupre
> Priority: Minor
> Fix For: 4.1.3
>
>
> Currently, in the request processing pipeline, Tapestry extracts the service information from the request in the requestCycleFactory method. This makes it cumbersome to write effective WebRequestServicerFilter and filter according to the service e.g. create a hibernate session for a page/externalpage/... service but not for an asset. Same for serializing requests: serialize page/external/... request but allow concurrent execution of an asset service.
> Could the service information be extracted earlier and be moved to the WebRequest object?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org