Allow service configurators to be arbitrary named and determine sevice by the
configuration parameter
-----------------------------------------------------------------------------------------------------
Key: TAPESTRY-1679
URL: https://issues.apache.org/jira/browse/TAPESTRY-1679
Project: Tapestry
Issue Type: New Feature
Components: tapestry-ioc
Affects Versions: 5.0
Reporter: Kalin Krustev
Assignee: Howard M. Lewis Ship
Fix For: 5.0.3
Threre's a strong pattern for service builders of the form:
Foo buildFoo(...) { ... }
In fact, virtually all service builders are of this form.
Seems like a Dont Repeat Yourself violation.
Foo build(...) {...}
seems completely reasonable; determine the service id from the service
interface name (the unqualified part).
Obviously, the current behavior would be left for the reasonable cases where
you need to provide a specific service id.
--
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]
