|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MGWT-340) util getInstance()... Samuele Arcidiacono (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Samuele Arcidiacono (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-340) util getInsta... Thomas Broyer (JIRA)

Thank you!
I may agree with you about the singleton, but the dependency injection pattern is often too verbose for GWT code meant to run in a browser.
For instance, I may not care about requesting a CssResource object using the getInstance() method.
The reason why I though this should need a fix is because it took me quite a while to track the error, and it might just get people stuck, when they attempt to create their first test.
I will report the bug to gwt-test-utils as well.