Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
5 of 5

ORMEvictEntity throws Unknown Entity for All Entities

Fixed

Description

(copied with some updates from the Hibernate Extension project as it didn't get filed there)

Tested in 5.2.8+50 and 5.3.1+38. For a test case, add an ORMEvictEntity("validEntity") call to any ORM app (e.g. a stock Contentbox install).

Any call to ORMEvictEntity will result in the following error. Note that the mapping is valid and we can perform an EntityLoad("School") immediately prior to the error being thrown. We can also dump the ORM Session factory for mapped beans and see the one we've requested.

Note that this also happens even if second level caching is disabling in Application.cfc or Lucee admin. As a quick workaround fix, you might just dodge whatever Lucee is doing here if L2 caching is disabled since ORMEvictEntity doesn't do anything and can be disregarded.

Environment

None

Details

Assignee

Reporter

Priority

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

Affects versions

Created 4 September 2018 at 11:51
Updated 22 November 2018 at 16:01
Resolved 12 October 2018 at 09:59

Activity

Show:

Samuel W. Knowlton5 November 2018 at 15:11
Edited

This issue is marked as fixed in 5.3.1.80 and Hibernate 3.5.5.73, but it still occurs in 5.3.1.87-RC, 5.3.2.4-SNAPSHOT, and 5.3.2.8-SNAPSHOT with Hibernate 3.5.5.73-SNAPSHOT.

Samuel W. Knowlton26 October 2018 at 15:11

Is this fix going to make it into 5.2 or just 5.3?

Samuel W. Knowlton12 October 2018 at 10:52

I don't know about the test case but we were using the correct case. Incorrect case in ORM entities causes plenty of other problems so we are pretty careful about it.

Michael Offner12 October 2018 at 09:29

Michael Offner12 October 2018 at 09:14

problem is in that case the name of the entity is case sensitive, so workaround make sure you are using the correct case for the name

Flag notifications