Which precise version of Railo is Lucee forked from?

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,

https://bitbucket.org/lucee/lucee/src/f76b47fdc3612b9ac95b77a24026889e5ebb615e/lucee-java/lucee-core/src/lucee/runtime/orm/hibernate/HibernateORMSession.java?at=master

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.

Thanks,
Julian.

[Snipped context from Discourse, first at the bottom]
3) Me:

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
in Lucee.

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?

  1. Micha:

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

  1. Me:

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 …

http://discourse.lucee.org/t/which-precise-version-of-railo-is-lucee-forked-from/128

Pretty sure I saw Micha respond to this question and confirm Lucee was forked from 4.2.1.008 and that all the patches applied to Railo also got applied to Lucee - without, presumably, the bug introduced for ORM in 4.2.2…

SeanOn Feb 2, 2015, at 9:12 AM, Julian Halliwell <@Julian_Halliwell> wrote:

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:

https://github.com/getrailo/railo/blob/39adf26638d45f99173aab6b9e9c6d2c8bf72dcc/railo-java/railo-core/src/railo/runtime/orm/hibernate/HibernateORMSession.java

with the corresponding java in Lucee,

https://bitbucket.org/lucee/lucee/src/f76b47fdc3612b9ac95b77a24026889e5ebb615e/lucee-java/lucee-core/src/lucee/runtime/orm/hibernate/HibernateORMSession.java?at=master

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.

Thanks,
Julian.

[Snipped context from Discourse, first at the bottom]
3) Me:

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 in Lucee.

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?

  1. Micha:

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 …

  1. Me:

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 …

http://discourse.lucee.org/t/which-precise-version-of-railo-is-lucee-forked-from/128

Micha, having run my ORM apps on Lucee for reasonable period now, these
seem to be the two issues:

https://bitbucket.org/lucee/lucee/issue/77/orm-doesnt-persist-data-in-cftransactions
https://bitbucket.org/lucee/lucee/issue/119/existing-orm-datasource-connections-fail

The symptoms appear to be slightly different from those in Railo 4.2.2 -
and not as bad. But they still need addressing for ORM folks to feel
confident migrating.On Monday, 2 February 2015 18:15:03 UTC, Micha wrote:

this is still on my radar and we will look into it

Micha

On Mon, Feb 2, 2015 at 7:12 PM, Julian Halliwell <julianh...@gmail.com <javascript:>> wrote:

If, as Micha said, the subsequent patches were also applied then
surely that would mean the ORM bug would still be present - since it
was introduced in one of those patches and never fixed.

He seemed to confirm this by saying Lucee was equivalent to 4.2.2.
Which is why I and the others affected have felt a bit nervous. 4.2.2
brought our prod server to its knees.

But the source suggests that particular commit at least wasn’t
applied. But there was another fix for nulls in those patches that I
actually wanted, having raised the issue. So it would be good to
understand exactly what was carried over and what wasn’t.

I know Micha’s busy, and maybe it’s on me to re-do all my
testing/issue raising. But if he could remember what happened that
would re-assure the ORM folks affected - and it wasn’t just me.

Cheers
Julian.

On 2 February 2015 at 17:51, Sean Corfield <se...@corfield.org <javascript:>> wrote:

Pretty sure I saw Micha respond to this question and confirm Lucee was
forked from 4.2.1.008 and that all the patches applied to Railo also got
applied to Lucee - without, presumably, the bug introduced for ORM in
4.2.2…

Sean