I know you’re busy, Micha, but could you possibly shed some light on this
for those of us using ORM who are apprehensive about migrating because of
the Railo 4.2.2 issues.
My testing shows the ORM transaction issue in Railo 4.2.2. is definitely
not present in Lucee. The ORM session timeout issue is harder to test, but
in dev it hasn’t cropped up.
Comparing the relevant source in R 4.2.2:
with the corresponding java in Lucee,
they appear to be significantly different despite what you said about Lucee
being equivalent to Railo 4.2.2.
Was the Hibernate session section actually rewritten in Lucee only,
perhaps to implement the Lucee-only multiple datasource feature?
If so, that would be great news. But would be good to have some clarity
before moving everything over.
[Snipped context from Discourse, first at the bottom]
I’ve only just migrated my dev Railo install to Lucee (which was indeed
pretty easy, nice work), but initial testing seems to indicate the issue -
RAILO-32731 https://issues.jboss.org/browse/RAILO-3273 - is not present
If that faulty 4.2.2.002 patch was indeed rolled into the current Lucee
release, then I wonder if the additional work on multiple ORM datasources
resolved it. Is it possible they are connected?
the fork was made starting this year, but all changes we did in Railo after
the fork, we did also in Lucee, so it is equivalent to to the latest 4.2.2
I know it’s 4.2 but is that the “stable” 4.2.1.008 version? Or was it from
the 4.2.2 preview? I ask because the latter contains serious issues with
ORM sessions …