A Non-Proposal related to Properties (original) (raw)
Mark Thornton mthornton at optrak.co.uk
Sat Mar 28 13:06:26 PDT 2009
- Previous message: A Non-Proposal related to Properties
- Next message: PROPOSAL: Simplified StringBuffer/StringBuilder syntax
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alan Snyder wrote:
A Non-Proposal related to Properties
This is not a proposal, but it seems related to Properties, so knowing that there are people on this list who are knowledgeable and care about Properties, I was hoping to get some useful feedback and suggestions. (I'll apologize in advance if this is old news...) As background, I have for a long time been a strong believer in static type checking and using methods for public access to data. Therefore, many years ago, when Java and JavaBeans decided to represent each property or attribute as a get/set method pair, I believed they made a good decision. However, after spending a year or two applying this approach to large sets of configuration parameters and winding up with huge interfaces and way too many wrapper classes, I have changed my mind. I know what you mean, but I'm not convinced by your solution. I'm tending to more delegation and use of the wrapper pattern with unwrapping to get at the configuration of delegated behaviour. This avoids those awful omnibus interfaces.
Mark Thornton
- Previous message: A Non-Proposal related to Properties
- Next message: PROPOSAL: Simplified StringBuffer/StringBuilder syntax
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]