On Thu, Jun 20, 2013 at 06:07:05PM -0400, John Burwell wrote: > Edison, > > As I mentioned in a previous email, it feels like a good place for > Path value object that encapsulates behavior. I propose we throw > this topic on the board for Sunday's Storage Architecture session, > and bring the resulting proposals back to the ML. > > <rant>To my mind, we overuse String throughout the codebase when we > should either be using richer types provided by the Java runtime > (e.g. java.net.URI) or defining custom value objects. In addition > to better levering the type checking of the compiler and potentially > exploiting polymorphism, rich value objects allow business rules to > be neatly encapsulated -- DRYing out the code base and allowing them > to reliably unit tested.</rant>
+1 to the rant. String is over-(ab)-used. Sometimes even to do XML. Happy to help moving all that if there's a plan you guys work out Sunday. Please bring it back to the lists. -- Prasanna., ------------------------ Powered by BigRock.com
