I'm working on a non-trivial app that uses this model (we submitted it), and I like it. :)
On Tue, Feb 26, 2008 at 11:00 AM, Sam Barnum <[EMAIL PROTECTED]> wrote: > IntelliJ does a good job of locating String usages of property names > when you refactor a property name, which is nice. Not sure if > Eclipse/Netbeans do this also. > > If you use CompoundPropertyModels then wouldn't refactoring your > business objects will still silently break code? > > It seems that ideally you'd just reference a property by its name, > and continue using things like CompoundPropertyModel, > PropertyResolver, etc. which accept string representations of > properties. Using a code generation tool + generation gap pattern is > a good way to accomplish this for now, have the code generation > template generate String constants for all your property names in the > generated entity superclass java file. > > All that said, this is a pretty nifty trick. I wonder how much it > will actually benefit developers, though. > > -Sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
