[jira] Updated: (TAP5-371) Service contribution methods should be able to include a parameter of type Logger (the service's logger), so as to give contributions the option to log with the service

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-371:
--------------------------------------

    Summary: Service contribution methods should be able to include a parameter of type Logger (the service's logger), so as to give contributions the option to log with the service  (was: Service contribution methods should be able to inlcude a parameter of type Logger (the service's logger), so as to give contributions the option to log with the service)

> Service contribution methods should be able to include a parameter of type Logger (the service's logger), so as to give contributions the option to log with the service
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-371
>                 URL: https://issues.apache.org/jira/browse/TAP5-371
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.0
>
>
> This would be handy for services where the contributions are active (code, not just data holders) and want to log; this means that logging by the contributions is done with any other logging for the service, which fits the sensibility that the contributions are part of the service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.