Timeline for Heavy use of static methods in a Java EE web application?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2015 at 9:03 | comment | added | Thorbjørn Ravn Andersen | Static methods are hard to test, so extensive use hint that the application lacks unit tests. | |
| Aug 5, 2013 at 15:40 | answer | added | user98757 | timeline score: 0 | |
| May 15, 2012 at 17:33 | answer | added | JasonTrue | timeline score: 4 | |
| May 15, 2012 at 11:49 | vote | accept | rlperez | ||
| May 15, 2012 at 5:44 | comment | added | gnat | (cont...) signs of good code in Java EE are same as in C#: understandable plain objects, consistent use of generics (or absence thereof - for pre-1.5 legacy code), DI/IOC in place of singletons, easy to understand synchronization. Anything other than that is under suspect | |
| May 15, 2012 at 5:15 | history | tweeted | twitter.com/#!/StackProgrammer/status/202265849904627712 | ||
| May 15, 2012 at 5:08 | comment | added | gnat | static final fields are thread safe due to strictly specified initialization procedure (see VM spec 2.17.5) - if you have only these, no need to worry. There is also a chance that framework guarantees that things are safely confined in one thread - if this is the case, framework specification explicitly states that - you need to check it before jumping to conclusions. Other than that the code stinks and I wouldn't wonder if there are data races | |
| May 15, 2012 at 3:41 | answer | added | Nick Klauer | timeline score: 7 | |
| May 15, 2012 at 3:21 | history | asked | rlperez | CC BY-SA 3.0 |