> 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.
Maybe, instead of adding properties, you could create subclasses? That seems like more of a natural fit for what you're trying to accomplish, if I understand you correctly. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Download the latest ColdFusion 8 utilities including Report Builder, plug-ins for Eclipse and Dreamweaver updates. http;//www.adobe.com/cfusion/entitlement/index.cfm?e=labs%5adobecf8%5Fbeta Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293224 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
