Yes, if it's just a simple matter of wanting extra properties in the object (properties that need no behavior), a generic getter and setter may be fine. The other options (writing a CFC to disk, composition, subclassing, or dynamically injecting methods) might be overkill or might not solve your particular problem.
On Nov 12, 2007 5:24 PM, Jeff Chastain <[EMAIL PROTECTED]> wrote: > The point is, this application is going to be used in different scenarios > where the concept of a user won't always be the same. In one situation, > employeeId might be a perfectly reasonable property for a user, while in > another scenario, it would have no meaning at all. Part of the admin user > interface allows the administrator to define new properties for objects - a > user, a product, etc - that pertain to their specific usage scenario. > > The dynaBean concept looks interesting, but it still appears to boil down > to a internal collection of properties with a get and set method that take > the name of a property and return its value. There may not be another way > to do this, I just thought I would ask and see. > > Thanks for the info. > -- Jeff > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293173 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
