Tapestry
  1. Tapestry
  2. TAPESTRY-1339

Rework Tapestry IoC to remove the concept of module ids and qualified service ids

    Details

    • Type: Improvement Improvement
    • 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

      As discussed on the mailing list, the cost/benefit ratio for qualified module ids is very high (in terms of adding complexity to the system) given that true name collisions are reasonably avoidable (in a system that will likely consist of between 5 and 10 modules for a particular application). Much of the documentation can be simplified greatly by treating service ids as (caselessly) unique, rather than qualified by a module id.

        Activity

          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