Grr. This comment system doesn't respect line breaks, so here it all is again:

OK, back in December I learned of one last refinement of my precompile.bat file. I'm so sorry that I've had to offer so many versions. I think this is the last, ultimate, one. And it solves various problems that had occurred while I tried to find this ultimate solution. Again, the following is just 3 lines, 2 sets and the java command:

set MX_INSTALL=c:\CFusionMX
set PATH=%MX_INSTALL%\runtime\bin;%MX_INSTALL%\runtime\jre\bin;%PATH%
java -classpath %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler
-webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

BTW, even though Updater 3 offers a new updater_compile.bat file, it's still not able to address some of the problems that this example does (like compiling code outside the cf root where the WEB-INF directory is).

OK, back in December I learned of one last refinement of my precompile.bat file. I'm so sorry that I've had to offer so many versions. I think this is the last, ultimate, one. And it solves various problems that had occurred while I tried to find this ultimate solution. Again, the following is just 3 lines, 2 sets and the java command:

set MX_INSTALL=c:\CFusionMX
set PATH=%MX_INSTALL%\runtime\bin;%MX_INSTALL%\runtime\jre\bin;%PATH%
java -classpath %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler
-webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

BTW, even though Updater 3 offers a new updater_compile.bat file, it's still not able to address some of the problems that this example does (like compiling code outside the cf root where the WEB-INF directory is).

Oops. Forgot to list the first line of the file. Here it is, now, complete:

set MX_INSTALL=c:\cfusionMX
%MX_INSTALL%\runtime\bin\java -classpath %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler -webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

Again, you need to change the first line to reflect wherever you installed CFusionmx.

(It's a shame we can't edit these comments. I'd like to go in and clean them all up!)

OK, sorry to have to correct things yet again, but it turns out that the solution to the updater 1 problem is really the fact that part of the compile process (when using the -f directive) seems to be needing the 1.4 JDK. You can get that (at least in my testing) by changing the second line in the command above to start with this instead:

%MX_INSTALL%\runtime\bin\java %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler -webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

That's 2 lines, with the second starting with a pointer to the runtim=bin rather than the runtime\jre\bin that I pointed to in the previous comment. Hope that helps folks.

Folks, I've learned that since the writing of this, the (Updater 1 for CFMX ) has broken the -f switch I mention for forcing a recompile. There's hope that this is addressed in Updater 2, as I've heard from some in MM.

Folks, while I warn in the article that you should not try to precompile your entire default cfusionmx\wwwroot directory, someone has just shared with me an experience that offers another reason not to. I'll share it for those who may be interested.

He had tried to run the precompile against it and got thousands of pages in error. Now, why he got so many errors is one thing. It may have been that his directory names included some with blank spaces (the precompiler doesn't like that, and will cause errors in compiling templates within them).

But more curious was that because of the errors, he was then unable to then execute the code in CFMX. Here are his comments:

> Those who want to compile an entire site or massive directory, may want to proceed with extreme caution. When I tried to do that it and got a boatload of error messages, it had a NASTY side effect.

>After compiling I did a refresh on my local site and BOOM; gone, dead. Every CFM template including the CF admin site, all resulted in page cannot be displayed. Restarting the CFMX server did no good. Finally the only thing that worked was to delete all of the java files that I had compiled and reboot the box. This finally restored CFMX to service again.

---

So, forewarned is forearmed. It seems that failures during the compile process cause a .java file to be left in the CFCLASSES directory (mentioned in the article) that then prevent the normal automatic compilation of code to even work. Yikes!

Let's see if I can format this well for display. It should be:

set MX_INSTALL=d:\cfusionMX
%MX_INSTALL%\runtime\jre\bin\java -classpath %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler -webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

Gads! Somehow the version of the precompile.bat file that was printed is missing some important code! :-(

It should be:

set MX_INSTALL=d:\cfusionMX
%MX_INSTALL%\runtime\jre\bin\java -classpath %MX_INSTALL%\lib\cfusion.jar coldfusion.tools.Compiler -webroot %1 -webinf %MX_INSTALL%\wwwroot\WEB-INF %1

As the article indicates, it's just 2 lines, the first being the SET and the second starting with %MX_INSTALL%.

But the printed version was somehow missing the beginning of the second line:

%MX_INSTALL%\runtime\jre\bin\java -classpath

So sorry for that printing mistake!

One other thing I've learned since writing the article is that it seems to fail to work if a directory name or file name being precompiled has spaces in the name.