> > If you do have a way to unify getters/setters into a property without > having to try and discover them I'd be interested to see. > First, I don't necessarily want to expose get/set methods. Second I don't necessarily want clients to discover them. That said, Swing is at the edge of the system as is JPA, distributed system calls. As I mentioned, things at the edge of a system need to have access to internal state and representation. That said you still need to be careful not to invert your lines of dependency. Using set/get or even properties for that matter is a great way to invert lines of dependency. Better to use a system of double dispatch such as is used with serialization.
IMHO, events and listeners should have been baked into the class hierarchy as they are in Smalltalk. This simplifies things enormously. Regards, Kirk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
