Details
Assignee
Michael OffnerMichael OffnerReporter
Pothys - MitrahSoftPothys - MitrahSoftPriority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Pothys - MitrahSoft
Pothys - MitrahSoftPriority
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 16 March 2022 at 14:31
Updated 1 June 2022 at 08:22
import definition of the component gets the import component from another cfc import definition with the same path & name.
For example, Consider the below codes have a different component in different directories that have an import definition with the same path & name (ex: import sub.importCFC ). The sub is the relative path to those components so sub it points out the different directories. First accessing the testApp1.accessImportinApp1() returns result as expected. After that, access the testApp2.accessImportinApp2() throws an error like The static member [ FROMAPP2 ] does not exist in the Component [ app1.sub.importCFC ], but there is a similar static member with name [ FROMAPP1 ] available. Here is a complete list of all available static members: [ FROMAPP1 ]. Seems It works as expected in ACF.
app1/testApp1.cfc
app1/sub/importCFC.fc
app2/testApp2.cfc
app2/sub/importCFC.cfc
Stacktrace: