[ http://issues.apache.org/jira/browse/TAPESTRY-712?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-712:
-------------------------------------------
Resolution: Won't Fix
The IMonitor interface should probably be deprecated; I've built up the request
processing pipelines, especially tapestry.request.WebRequestServicerPipeline,
as a better way to add cross-cutting concerns, such as transaction management,
to a Tapestry application.
> Provide more information to IMonitor listeners
> ----------------------------------------------
>
> Key: TAPESTRY-712
> URL: http://issues.apache.org/jira/browse/TAPESTRY-712
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Alexander Kundirenko
>
> Hello
> Could you change IMonitor methods signatures to provide more information to
> monitor?
> F.e. change:
> from: void serviceBegin(String serviceName, String detailMessage);
> to: void serviceBegin(Service service, Infrastructure infrastructure);
> Corresponding change in AbstractEngine:
> from: monitor.serviceBegin(service.getName(),
> _infrastructure.getRequest().getRequestURI());
> to: monitor.serviceBegin(service, _infrastructure);
> I tried to implement transaction management in monitor and was faced with
> the problem: it is impossible to obtain Http Session within monitor listener.
> Thank you
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
