[TAP5-2012] Make multiple same name service decoration methods error message better

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.4
• Component/s: tapestry-ioc
• Labels: month-of-tapestry
• Assignee: Thiago Henrique De Paula Figueiredo
• Reporter: Ville Virtanen
• Created: 10/Oct/12 18:11
• Updated: 06/Jun/14 14:52
• Resolved: 06/Jun/14 14:52

Description

If one has many decoration methods that are named exactly the same way the other decoration is silently dropped with log warn "Could not add object with duplicate id 'ServiceInterfaceName'. The duplicate object has been ignored."

This error message could be greatly improved if it would clearly state that there are multiple decoration methods that have the same name, and additionally it would be nice to provide the list of modules that do have the problematic methods.

It could further be improved by having the possible fix in the message, that is to use Match annotation and to match the service interface and to change the name of the method.

It would also be nice touch to mention in the log message which method won this time as it seems that is somewhat random, and would be useful later when diagnosing problems.

Issue Links

• relates to: TAP5-1305 Service decorations can fail if using the conventional naming