[
https://issues.apache.org/jira/browse/TAP5-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship resolved TAP5-1062.
----------------------------------------
Resolution: Invalid
In retrospect, the one-parameter bind() call was probably a mistake, as it
obscures (to the IDE or other tools) which classes are actually used.
> It would be nice if ServiceBinder had a method that allowed an arbitrary
> number of standard services to be defined
> ------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1062
> URL: https://issues.apache.org/jira/browse/TAP5-1062
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> A standard service is one where the implementation class is in the same
> package as the service interface, and is named with an "Impl" suffix. In
> other words, instead of:
> public static void bind(ServiceBinder binder) {
> binder.bind(EntitySelectModelSource.class);
> binder.bind(SelectModelResponseGenerator.class);
> binder.bind(AuthenticationService.class);
> binder.bind(TimeService.class);
> You could write:
> public static void bind(ServiceBinder binder) {
> binder.bindStandard(EntitySelectModelSource.class,
> SelectModelResponseGenerator.class, AuthenticationService.class,
> TimeService.class);
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
