Tapestry
  1. Tapestry
  2. TAPESTRY-1341

Allow service builders named "build" and determine service id from the result type

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.3
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development