Status/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): A. Bakia / A. Bakia (A. Bakia)
Created: 09/01/2009
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 9,0,0,241018 / 260230
Priority/Frequency: Normal / Most users will encounter
Locale/System: English / Win All
Vote Count: 0
Problem:
This concerns the cfc attribute of the tag cfajaxproxy. The cfajaxproxy apparently only works if the component is inside the web root. That is quite restrictive, as there are many use cases in software development that require the CFC to be outside the web root.
Method:
Put the cfc to be proxied, proxy.cfc, in any directory off the webroot, for example, c:\temp\test\proxy.cfc.The following values for the cfc attribute fail. In each case Coldfusion tells you it cannot find the cfc.(1) Define the mapping testMapping in the Administrator as followslogical path: /testMapping directory path: c:\temp\testThen do <cfajaxproxy cfc="testMapping.proxy" jsclassname="proxy"> or <cfajaxproxy cfc="/testMapping.proxy" jsclassname="proxy"> This fails because the value of the cfc attribute may not be a mapping.(2) The relative-path versions <cfajaxproxy cfc="..\..\..\..\..\temp.test.proxy" jsclassname="proxy"> or <cfajaxproxy cfc="..\..\..\..\..\temp\test\proxy.cfc" jsclassname="proxy"> don't work either because the path may not begin with a dot.(3) <cfajaxproxy cfc="c:\temp\test\proxy.cfc" jsclassname="proxy"> fails, even though the documentation says the cfc attribute can be the absolute path.
Result:
The specified CFC /testMapping.test.proxy could not be found. The path to the CFC must be specified as a full path, or as a relative path from the current template, without the use of mappings.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3039843
External Customer Info:
External Company:
External Customer Name: A. Bakia
External Customer Email: 4E2913DC4455DE13992016B6
External Test Config: 09/01/2009Attachments:
Comments: