Geek Answers Handbook

CFC expands folder for sisters

I saw all kinds of solutions for the cfcs extension in the parent folders with access to the parent files or CF administration, but I did not see a workable solution for the cfc extension in the shared / sibling folder without access to the parent folders.

Does this solution require access to the parent folders? (I don't know what these mappings are, but I don't have access to Application.cfc)

This solution requires the ability to create an application.cfc application that does not work for me (creating one of them in myApp does nothing, because the environment in which I include the index page in myApp and builds from there ... the client never directly calls its for application recognition application.cfc)

For instance:

  • Wwwroot / some / path / MYAPP / Shared / Base.cfc
  • Wwwroot / some / path / MYAPP / Function / Function.cfc

I am looking to be able to call functionality in Base.cfc (which contains the common methods used in the application) from the Function.cfc function through super and extension.

I have access to all the files in myApp, but not to "wwwroot", "some" or "path."

To extend Base.cfc inside Function.cfc, I have to extend the full path to "some.path.myApp.Shared.Base". This can cause problems if someone renames the myApp folder, since I would have to manually edit each Function.cfc that extends Base.cfc

, "" , , , , , CFC, Base.cfc.

( "..Shared.Base" ), , CFC myApp, , myApp . (MyApp.Shared.Base)

Application.cfm Coldfusion.

+5
5

: .

, . - .

, ( ):

<cfscript>

    path1 = GetDirectoryFromPath(cgi.SCRIPT_NAME);
    path2 = ListToArray(path1, "/");
    path3 = path2;
    path3[ArrayLen(path3)] = "shared";
    path4 = ArrayToList(path3, ".");
    path5 = ArrayToList(path2, ".");

    myBase = CreateObject("component", "#path4#.Base");

    myFunction = CreateObject("component", "#path5#.Function").init(myBase);

</cfscript>

Function create init:

<cffunction name="init">
    <cfargument name="base">
    <cfset variables.Base = arguments.base />
    <cfreturn this />
</cffunction>

, , .

+2

Base.cfc cfc, Base.cfc cfc .

, cfc :

<cfinclude template="../shared/base.cfc" />

cfc .

+1

- .

, CF, , . , - , , .

0

/ reset...

, , ...

<cfabort>
<cfcomponent extends="{sharedpath}.Base">
...

application.cfc - ...

<cfdirectory name="codetemplates" action="list" directory="wwwroot/some/path/myApp/codetemplates" />
<cfloop query="codetemplates">
    <cffile name="temp" action="read" path="#tempfilepath##filename#" />
    <cfset newfilecontent = replace(temp.filecontent, '{sharedpath}', configvarwithrightpath) />
    <cfset filecontent = replace(newfilecontent , '<cfabort>', '') />
    <cffile name="temp" action="write" path="#livefilepath##filename#" />
</cfloop>

, , cfc .

0

? , "" cfcs, .

, :

  • Wwwroot///MYAPP/Shared/Base.cfc
  • Wwwroot///MYAPP//Function.cfc

:

  • Wwwroot///MYAPP//Base.cfc
  • Wwwroot///MYAPP//Function.cfc

<cfcomponent extends="Base"></cfcomponent>

However, if you have / require several folders of "functions", you can do something like this. Place a Proxy.cfcinside each function folder with this code:

<cfcomponent extends="some.path.myApp.shared.Base"></cfcomponent>

And then each cfc in folders with "functions" will expand its local Proxy.cfc( extends="proxy"). This gives you 1 proxy per folder, which is still not perfect, but less of a hassle than updating each cfc.

0
source

More articles:


All Articles