I think it and Sean's coding standards document have struck up a friendship, they've been in there so long.
:)
The only thing so far has to do with his recommendation of adding a ColdFusion mapping for /com but even that is only an issue due to his recommendation that you map it to /WEB-INF/cfcomponents/com. �I seem to remember there being a bug with CF mappings into the WEB-INF directory not working properly. �Everything else looks to be > excellent.
I agree with your concern - I wouldn't put anything inside /WEB-INF because I view it as a 'system directory'. We have our components mapped outside the wwwroot which provides the same security (CFCs can't be accessed via URLs; we only put Web Service Facades under wwwroot). In our CFMX for J2EE install, we actually have the CF files totally outside the JRun install tree and map the document root (I documented this on my blog way back) and we don't have a /WEB-INF under our CF tree. We can easily clone our installs now because our build system targets one directory tree on the server and the CFMX / JRun install lives in another directory tree - so we can just clone the JRun tree onto a new server and then run a build to push the latest CF content there from CVS.
As for the rest of MVCF, I like what I've read but you can read my thoughts in more depth here:
http://www.corfield.org/blog/archives/2002_12.html#000059
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
