Indeed, it seems a nice way to organise your CFMX code.
We do something similar (no files under Jrun4/CFMX installation).
Here is our structure (that we use with CFMX Pro/Ent or CFMX for J2EE) :
d:/applications >> ColdFusion pages accessible through HTTP
d:/applications/www.myappA.com - an application A (only layout CFM pages and
SWF app), document root of an Apache Virtual host
d:/applications/www.myappB.com - an application B (only layout CFM pages and
SWF app), document root of an Apache Virtual host
d:/applications/CF-INF/ >> ColdFusion components, lib...
d:/applications/CF-INF/ - XML config files for all the applications
d:/applications/CF-INF/cfcomponents - CFC root (business/data components)
shared across all the applications on the server
d:/applications/CF-INF/cfpagelets - Pagelets root (view components) shared
across all the applications on the server
d:/applications/CF-INF/cflibs - UDF Lib root shared across all the
applications on the server
d:/applications/CF-INF/cftags - CF custom tags shared across all the
applications on the server
d:/applications/CF-INF/lib - Java libraries root
d:/applications/CF-INF/fla - Flash source root
d:/files >> Static files
d:/files/www.myappA.com/i18n - properties files for internationalization of
application A
d:/files/www.myappA.com/cache - cache root
d:/files/www.myappA.com/mappingA - an example of Apache mapping for static
files (for example /images)
(in our case, all the static files are on a dedicated files server running
only Apache, files.myappA.com)
d:/database >> database files root
Then we add the following mappings in jrun.xml :
<virtual-mapping>
<resource-path>/CF-INF</resource-path>
<system-path>d:/applications/CF-INF/</system-path>
</virtual-mapping>
<virtual-mapping>
<resource-path>/com</resource-path>
<system-path>d:/applications/CF-INF/cfcomponents/com</system-path>
</virtual-mapping>
We use package naming convention for all our CFC and pagelets (no possible
name conflicts between the different applications).
Like this you can call any CFC by cfinvoke "com.mycompany.myCFC",
"com.myappA.anotherCFC", any Lib by cfimport "/CF-INF/lib/mylib.cfm" ...
Benoit Hediard
www.benorama.com
PS : for the application name, we use the following convention :
- www.myappA.local : application running on the local machine (usually
developer's one),
- www.myappA.dev : application running on the development server (code
reference with source control),
(- www.myappA.test : application running on the test/staging server if you
have one)
- www.myapp.com : application running on the production server(s).
> -----Message d'origine-----
> De : Sean A Corfield [mailto:[EMAIL PROTECTED]
> Envoyé : samedi 15 mars 2003 09:28
> À : CF-Talk
> Objet : Re: CFC's - Where to put them?
>
>
> On Saturday, Mar 15, 2003, at 00:12 US/Pacific, Dave Carabetta wrote:
> >> As for messing with WEB-INF - I would definitely not recommend that!
> > Can you briefly elaborate why?
>
> I'd consider it a 'system directory' and subject to change without
> notice... :)
>
> >> Here's what we do (for CFMX for J2EE on JRun 4):
> >>
> >> /data
> >> /www
> >> /appserver
> >> /cfmx
> >> /config
> >> ...mapped in CF Admin...
> >> /extensions
> >> /components
> >> ...in Custom Tag Paths...
> >> ...tree of CFCs...
> >> /customtags
> >> ...in Custom Tag Paths...
> >> /includes
> >> ...mapped in CF Admin...
> >> /wwwroot
> >> ...cfm files...
> >> /jrun
> >> ...JRun 4 installation...
> >> /servers
> >> /cfmx1
> >> ...server instance...
> >> /cfmx2
> >> ...server instance...
> >> /lib
> >> ...shared (Java) libraries...
> >> /httpd
> >> /apache
> >> ...Apache 1.3.x for gif/html etc...
> >> /apache2
> >> ...Apache 2.0.44 for dispatching request...
> >> /sites
> >> /www.macromedia.com
> >> /docs
> >> ...HTML/GIF assets...
> >
> > Can I be a pain in the a** and ask you to clarify the above directory
> > structure? I'm a little confused as to where some of these directories
> > are
> > in relation to each other.
>
> Oh, didn't the tabs show the indentation?
>
> /data/www/appserver/cfmx/ - all the CF source code
> /data/www/appserver/cfmx/config/ - XML / cfm configuration files
> /data/www/appserver/cfmx/extensions/components/ - CFC tree
> /data/www/appserver/cfmx/extensions/customtags/ - custom tags
> /data/www/appserver/cfmx/extensions/includes/ - mapped directory of
> includes
> /data/www/appserver/cfmx/wwwroot/ - cfm docroot
> /data/www/appserver/jrun/ - JRun 4 installation
> /data/www/appserver/jrun/servers/cfmx1/ - a CFMX for J2EE server
> instance
> /data/www/appserver/jrun/servers/cfmx2/ - a CFMX for J2EE server
> instance
> /data/www/appserver/jrun/servers/lib/ - Java libraries and config files
> used by our CF apps
> /data/www/httpd/apache/ - Apache 1.3.x installation
> /data/www/httpd/apache2/ - Apache 2.0.44 installation
> /data/www/sites/www.macromedia.com/docs/ - HTML docroot
>
> > Why do you
> > feel that the separation you've come up with is the ideal setup?
>
> Because we have many servers with many different software install
> configurations, we have a standardized directory structure for
> installing pretty much anything. It works for us.
>
> Having the CF stuff outside JRun is nice in terms of separating our
> source code from the product installation directories (see my blog for
> commentary on maintaining multiple CFMX for J2EE server instances with
> a shared document root).
>
> > I'm embarking on a large-scale project for CFMX on JRun 4 and I spent
> > a good
> > portion of the day today trying to figure out the best way to
> > structure my
> > templates and directories (the timing of your post couldn't be
> > better!).
>
> Hope this is useful to you?
>
> Sean
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at http://www.coolfusion.com
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
