Comments on: Application.cfc Mappings Gotcha https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/ Thoughts, rants, and even some code from the mind of Barney Boisvert. Thu, 11 Sep 2014 09:58:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Julian Halliwell https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-132123 Julian Halliwell Fri, 10 Oct 2008 16:44:16 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-132123 Hurray, the docs have been corrected. Hurray, the docs have been corrected.

]]> By: Julian Halliwell https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-130795 Julian Halliwell Mon, 06 Oct 2008 09:42:40 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-130795 Submitted another reminder to Adobe, and they've responded with: "We will be correcting this soon enough." Sheesh, I wonder what kind of version control/workflow system they have that makes it too complex to just add a couple of slashes. Whatever it is, sticking to it is obviously more important to them than avoiding wasting their customers' time. Submitted another reminder to Adobe, and they've responded with: "We will be correcting this soon enough." Sheesh, I wonder what kind of version control/workflow system they have that makes it too complex to just add a couple of slashes. Whatever it is, sticking to it is obviously more important to them than avoiding wasting their customers' time.

]]> By: Julian Halliwell https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-129471 Julian Halliwell Thu, 02 Oct 2008 08:39:28 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-129471 Barney, my experience is the same as Ike's, that the forward slash is required for all mappings, alphanumeric or otherwise. It was me who originally reported the mistake in the Livedocs soon after the CF8 release and they did correct their examples fairly promptly. But for some reason the correction got "reverted" some months later, which I again reported. Adobe replied saying they would try and found out what happened and just post my comment in the meantime. But they don't seem to have done anything to "re-correct" the docs, which means it continues to cause confusion/frustration unless you read the comments. Cheers Julian. Barney, my experience is the same as Ike's, that the forward slash is required for all mappings, alphanumeric or otherwise.

It was me who originally reported the mistake in the Livedocs soon after the CF8 release and they did correct their examples fairly promptly. But for some reason the correction got "reverted" some months later, which I again reported. Adobe replied saying they would try and found out what happened and just post my comment in the meantime. But they don't seem to have done anything to "re-correct" the docs, which means it continues to cause confusion/frustration unless you read the comments.

Cheers
Julian.

]]> By: ike https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-129251 ike Wed, 01 Oct 2008 18:16:35 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-129251 Umm... well you don't have to be a jerk about it, but no, the point of Application.cfc mappings is to have application-specific mappings, which is entirely different than application relative mappings. Without going at all out of my way to try and find them I've seen a dozen or so different blog entries or mailing list threads where someone was royally confused by the fact that they needed to add a forward-slash in front of the name of the mapping (and in my experience that's been true whether there was an underscore in it or not). So I don't think it's unfair to say that it's nice to be able to simply declare a mapping as addMapping("coldspring","../coldspring") to avoid all that confusion and to avoid having to manually perform the extra getDirectoryFromPath(getCurrentTemplatePath()). I suppose similar comments from the Grails guys would be acceptable to you tho. Umm… well you don't have to be a jerk about it, but no, the point of Application.cfc mappings is to have application-specific mappings, which is entirely different than application relative mappings. Without going at all out of my way to try and find them I've seen a dozen or so different blog entries or mailing list threads where someone was royally confused by the fact that they needed to add a forward-slash in front of the name of the mapping (and in my experience that's been true whether there was an underscore in it or not). So I don't think it's unfair to say that it's nice to be able to simply declare a mapping as addMapping("coldspring","../coldspring") to avoid all that confusion and to avoid having to manually perform the extra getDirectoryFromPath(getCurrentTemplatePath()). I suppose similar comments from the Grails guys would be acceptable to you tho.

]]> By: barneyb https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-129041 barneyb Wed, 01 Oct 2008 05:51:03 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-129041 ike, Application root relative mappings are the whole point of Application.cfc mappings. If they weren't application root relative, you'd just use a server-level mapping. E.g.: <cfset THIS_DIR = getDirectoryFromPath(getCurrentTemplatePath()) /> <cfset this.mappings["/coldspring"] = THIS_DIR & "lib/coldspring" /> onTap gives you the plugin directory construct (which is easily accomplished other ways as well), but there's nothing onTap-ish about relative mappings. ike,

Application root relative mappings are the whole point of Application.cfc mappings. If they weren't application root relative, you'd just use a server-level mapping. E.g.:

<cfset THIS_DIR = getDirectoryFromPath(getCurrentTemplatePath()) />
<cfset this.mappings["/coldspring"] = THIS_DIR & "lib/coldspring" />

onTap gives you the plugin directory construct (which is easily accomplished other ways as well), but there's nothing onTap-ish about relative mappings.

]]> By: ike https://www.barneyb.com/barneyblog/2008/09/30/applicationcfc-mappings-gotcha/comment-page-1/#comment-129034 ike Wed, 01 Oct 2008 05:18:36 +0000 http://www.barneyb.com/barneyblog/?p=514#comment-129034 One of the new config directories in version 3.2 of the onTap framework (aside from IoC configs) is for mappings, which is neat. It will actually allow plugins to create their own application-specific mappings when you install them. I don't expect most plugins to need it, but it's handy to have. The configs use a method call to set the mapping, so in addition to ensuring that they have that leading slash, it also allows the mappings to be relative from the application's root directory. :) One of the new config directories in version 3.2 of the onTap framework (aside from IoC configs) is for mappings, which is neat. It will actually allow plugins to create their own application-specific mappings when you install them. I don't expect most plugins to need it, but it's handy to have. The configs use a method call to set the mapping, so in addition to ensuring that they have that leading slash, it also allows the mappings to be relative from the application's root directory. :)

]]>