I remember Sean mentioned at one point that he had written a script to pre-create all the reactor objects enumerated in his XML file at one once. There are a couple benefits to this... for one thing, it validates your objects and XML before you get busy building an application. For another it can speed development up a bit.
So I built this little CFC that takes the path to the reactor XML file and "compiles" your reactor model in it's entirety. It has output that gives the number of reactor objects, uses cfflush to keep the user informed of what's being compiled at any given point in time, can be run in the URL (the run() method's access attribute is marked remote), and gives you the total time elapsed once it's all over.
I don't know if anyone else will ever use it, but it works ok for me... figured I'd share it on the off chance that someone else might find it useful.
A sample call might be:
<cfset compiler = createObject("component","ReactorCompiler").init(expandPath('./reactor/cforeactor.xml'))>
<cfset compiler.run()>
That can be shortened to
<cfset createObject("component","ReactorCompiler").run(expandPath('./reactor/cforeactor.xml'),false)>
Or you can hit it this way:
The boolean argument to run() controls whether or not the compiler deletes your volatile project files under the reactor home folder before running the rest of the process. It doesn't know your custom files exist, so it won't delete them, just /reactor/project/{projName}.
Laterz,
Laterz,
Jared Rypka-Hauer
------------------------------------------------
Jared C. Rypka-Hauer
Continuum Media Group LLC
Member, Team Macromedia - ColdFusion
"That which does not kill me makes me stranger." - Yonah Schmeidler
