You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Ville Virtanen (JIRA)" <ji...@apache.org> on 2012/10/10 20:13:03 UTC
[jira] [Created] (TAP5-2012) Make multiple same name service
decoration methods error message better
Ville Virtanen created TAP5-2012:
------------------------------------
Summary: Make multiple same name service decoration methods error message better
Key: TAP5-2012
URL: https://issues.apache.org/jira/browse/TAP5-2012
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Reporter: Ville Virtanen
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 sue 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 in later when diagnosing problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2012) Make multiple same name service
decoration methods error message better
Posted by "Ville Virtanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ville Virtanen updated TAP5-2012:
---------------------------------
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.
was:
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 sue 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 in later when diagnosing problems.
> Make multiple same name service decoration methods error message better
> -----------------------------------------------------------------------
>
> Key: TAP5-2012
> URL: https://issues.apache.org/jira/browse/TAP5-2012
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Ville Virtanen
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2012) Make multiple same name service
decoration methods error message better
Posted by "Ville Virtanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ville Virtanen updated TAP5-2012:
---------------------------------
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.
was:
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 sue 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 in later when diagnosing problems.
> Make multiple same name service decoration methods error message better
> -----------------------------------------------------------------------
>
> Key: TAP5-2012
> URL: https://issues.apache.org/jira/browse/TAP5-2012
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Ville Virtanen
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira