This thing that bugs me about this approach is that you are defining a sub-class for the sake of making "neater" code. You don't actually want a subclass, but it's a side effect of the approach. And being a subclass it can cause further problems.
I'm happy to take coding shortcuts but I'd put the model first and the code second. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
