[TAPESTRY-1339] Rework Tapestry IoC to remove the concept of module ids and qualified service ids

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.0.3
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 09/Mar/07 19:48
• Updated: 11/Mar/07 19:22
• Resolved: 11/Mar/07 19:22

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.