[TAPESTRY-1341] Allow service builders named "build" and determine service id from the result type - ASF JIRA

XML

Word

Printable

JSON

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.

is cloned by

TAP5-69 Add annotation, @Contribute, to allow service contributor methods to be arbitrary named

is related to

TAP5-69 Add annotation, @Contribute, to allow service contributor methods to be arbitrary named