Your FormProc enhancements, coupled with opt-formproc sound very promising. I look forward to using it.
There's another twist in there that you might like as well =;)
I'm going to make in an optional compile, but the package also includes a Maverick controller designed to work with both FormProc and the new Commons Chain package in the Commons. This lets you specify the form to validate and the business class to run all from the Maverick config. By default, the name of the business command (or chain of business commands) is the same as the form, but can also be different.
The business commands are given logical names through a simple configuration file, like this:
<chains>
<command
name="cpu_permit_insert"
className="us_ok_deq_wqdata.command.PermitInsert" /> <command
name="cpu_permit_select"
className="us_ok_deq_wqdata.command.PermitSelect" /> <command
name="cpu_permit_update"
className="us_ok_deq_wqdata.command.PermitUpdate" /></chains>
The command is passed a context (like a Maverick or Velocity Context) which is passed to any other command in the chain, and then back to the caller.
-Ted.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf [INVALID FOOTER]
