There are several ways you could tackle this, the least of which could be setting a default value in the database... cooler, maybe, would be to use the record's transfer object, or perhaps add a generic controller/ message that takes the field name as an argument, and does the magic there...
Really a bunch of different ways without having to dig into the core... Not sure how they compare in ease of use... that's up to preference I guess? The "reactor" way will require an edit to each object that needs the "massaging", the MG way will need to broadcast a message where ever you save one of those objects... The reactor way would be best*, if not in the DB itself, as then whenever you do something with the object you can expect it to behave the same way. *maybe :-) HIH! On 3/26/07, Bob S wrote:
Hi all, I'm using Reactor with Model-Glue, and I'm using makeEventBean() in my controller to grab all of the values from a submitted form and place them into my reactor record object. This works very well, except for the often frustrating html checkbox issue. That is, when you submit a form with a checkbox, and the checkbox isn't checked, nothing is submitted with your form. Therefore, makeEventBean() cannot set my record object correctly when a user un-checks a field as that information is not passed to it.
... -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
