[
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.3)
4.1.4
> 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.4
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
