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 >Yes I don't think I'm following what you're trying to do. If employeeID is a >property of the User object, why wouldn't it already be there from the >start? I'm not clear on what the "end user of the application" has to do >with it. > >On Nov 12, 2007 2:01 PM, Jeff Chastain <[EMAIL PROTECTED]> wrote: > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion is delivering applications solutions at at top companies around the world in government. Find out how and where now http://www.adobe.com/cfusion/showcase/index.cfm?event=finder&productID=1522&loc=en_us Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293163 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
