Hi, In some of the Wicket code we may see method signatures like: - protected static - private static - private final
I wonder what are your reasons to use them ? - do they improve performance ? - do they save some bytes ? (in PermGen maybe ?!) - do you need the 'static' just for the unit tests ? - something else My drivers to touch such signatures are: - I don't see a reason to have 'final' in 'private final' method. And my IDE also notifies me about this. - Scala has problems seeing 'protected static' methods from Java. I want to check with you before modifying them. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
