In my Bean CFCs I have the standard methods: getSomeProperty(), setSomeProperty(), getInstance(), setInstance(), and validate(). What I am toying with is "how much" data/meta data should/could I store about the properties within the bean and how much (if any) might be better suited for "properties file" such as an XML file. What would be nice is to have some meta data about the properties themselves for different purposes:
form element attributes: maxlength,id,name,label cfqueryparam attributes: maxlength,null (evaluate expression), cfsqltype javascript validation server side validation (within the Bean's validate method) My question is... how much of this "meta data" would/could/should be stored in the Bean itself and how much would be better suited for a properties file of some sorts... and is all this even worth it? Say for instance, a required field changes or a field's maxlength increases from 500 characters to 1000, it would be nice to denote that in one area and have that piece of meta data accessible anywhere the property is used. Is all this overkill? I haven't implemented anything yet but I can definitely see some benefit of doing so. Your thoughts? Tango. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
