You are right on how to deal connections.
Contributing to tapestry.request.WebRequestServicerPipeline can be replaced
by a threaded service.
This has the advantage of doing things when they are needed to do.
Mit freundlichen Grüßen
Michael Frericks
|---------+---------------------------->
| | |
| | |
| | Ron Piterman |
| | <[EMAIL PROTECTED]|
| | t> |
| | Gesendet von: |
| | news |
| | <[EMAIL PROTECTED]|
| | rg> |
| | |
| | |
| | 13.12.2005 11:48 |
| | Bitte antworten |
| | an "Tapestry |
| | users" |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| An: [email protected]
|
| Kopie:
|
| Thema: Re: Tapestry4 setupForRequest "replacement"? [Virus
checked] |
>------------------------------------------------------------------------------------------------------------------------------|
no no no... look at my fresh post in reply to this thread - there is a
much better way of doing just what you want.
[EMAIL PROTECTED] wrote:
> Hi,
>
> i move the code from setupForRequest and cleanupAfterRequest
> to a service implementing the interface
> org.apache.tapestry.services.WebRequestServicerFilter
> and contribute this service to the configuration-point
>
> tapestry.request.WebRequestServicerPipeline
>
> example:
>
> <service-point id="WorkflowRequestFilter"
> interface="org.apache.tapestry, also because it is , also because it is
.services.WebRequestServicerFilter">
> <invoke-factory>
> <construct
>
class="de.sparkasseninformatik.comserv.tapui.workflow.WorkflowRequestFilter">
> <set-object property="applicationStateManager"
> value="service:tapestry.state.ApplicationStateManager"/>
> <set-object property="workflowEngine"
> value="service:de.sparkasseninformatik.comserv.workflow.WorkflowEngine"/>
>
> </construct>
> </invoke-factory>
> </service-point>
>
> <contribution
> configuration-id="tapestry.request.WebRequestServicerPipeline">
> <filter name="WorkflowRequestFilter"
> object="service:WorkflowRequestFilter"/>
> </contribution>
>
> inside the method 'service' you can thing like:
>
> public void service(WebRequest request, WebResponse response,
> WebRequestServicer servicer) throws IOException
> {
> _requestGlobals.store(request, response);
>
> try
> {
> before(request, response);
> servicer.service(request, response);
> }
> finally
> {
> after(request, response);
> }
> }
>
> Mit freundlichen Grüßen
>
> Michael Frericks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
