> > I have never had a problem with this. We do not have any custom tag > > paths or other paths set up in the administrator, and all files on our > > site can find all cfcs on our site, using a reference from the > > webroot. > > I have been corrected. We have one mapping and one custom tag path: > > mapping: /CFIDE D:\apps\CFusionMX\wwwroot\CFIDE > custom tag path: D:\apps\CFusionMX\CustomTags > > I think these are the defaults, correct?
True. The only potential problem with this is that the WebRoot is the last thing searched - if you ever do put in a mapping (or are on a shared server and somebody else puts in a mapping) those mappings will be searched before your root - so any CFCs with conflicting names will be hosed. There's also a more general potential issue with name conflicts. If you roll all your own CFCs then no problem, but if you start using third party applications then you might have conflicts - using the web root method you're not guaranteed to get the right CFC in that case. Neither of these should prevent you from doing what you're doing - they're both just things to keep in mind. Jim Davis ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
