Fixed
Details
Assignee
Pothys - MitrahSoftPothys - MitrahSoftReporter
Rory LaitilaRory LaitilaPriority
NewLabels
Fix versions
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
Sprint
NoneAffects versions
Details
Details
Assignee
Pothys - MitrahSoft
Pothys - MitrahSoftReporter
Rory Laitila
Rory LaitilaPriority
Labels
Fix versions
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
Sprint
None
Affects versions
Created 3 August 2021 at 18:57
Updated 15 March 2022 at 12:56
Resolved 15 March 2022 at 07:43
Component paths imported into ORM entities created with entityNew() or entityLoad() cannot be instantiated. On Lucee 5, instantiated imported components raises the error: "invalid component definition, can't find component". This does not happen on Lucee 4..
Steps to reproduce:
Download provided sample application and unzip it
With command box, cd to the unzipped directory
Run a Lucee instance with CommandBox: server start
When Lucee has started, manually install H2 database extension in the Lucee Admin. URL path to Lucee Admin is /lucee/admin/web.cfm . Go to Extensions > Applications. Select H2 from the list and install
Go to /index.cfm, it will fail and show the error
Below are snippets from the attached zip file for quick reading. Download the zip that includes the Application.cfc ORM setup code in order to execute this code
Snippet of the example BasicEntity which instantiates a component. What works is instantiating via relative paths, or application mappings expected. What fails is instantiating from an imported component path, does not work on Lucee 5.
Executing the code with the following scenarios and resulting behavior:
Lucee 5 will throw the following error when executing the test case: