> But mostly I would say that an object that takes that many arguments is > probably doing too much.
I would generally agree, except that for my last project this was what the boss wanted/ part of the design. Think: multi-tabbed forms, 150+ potential form elements. Think: complex app perfectly suited for FLEX but done in DHTML.... > Or that the coder is hard-coding static > configuration values that should be in an xml file somewhere. hmmm... I see your point but personally I'm really not keen in having vital information like that in a seperate XML file. the concept leaves me real cold. (using a bean as an example) you could go a step further and have a single DTO bean for the whole darn lot that does nothing except processes all DTO work using external XML files. So the XML files hold all the vital information. Again, I'm looking at this from a maintainance/maintability point of view... I could be the one out of step and this "XML to drive the arguments" idea is very widespread... anyone else with 2c to share? additional: and heaven help you if there was micro-logic to inset in there: "if this key exists then make sure that another other keys exists" or "if AA value is a string than make sure that BB is an integer else it's BB is an optional string".... the afore mentioned project was full of this sort of BS.... ---------------------------------------------------------- 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]
