Incompatibility with Railo - how to solve it

[Pedro Martins]

I found out how to solve a Reactor-Railo incompatibility so I'll
explain it as reactor developers may want to correct this, making
Reactor full compatible with Railo.

I picked a backoffice app that I developed with Adobe ColdFusion and
tried to migrate it to Railo. After just 3 minor changes I was able to
run the application and almost all its functionalities on Railo. Only
one thing didn't work, a very specific case. I had a news object that
has some themes associated. When I edited the news object, if I
removed some theme's checkbox, the commiting would fail.

I got an error on reactor/iterator/iterator.cfc line 156 as reactor
tries to check for an arguments variable in a list. Reactor looks for
useTransaction, Railo has it like USETRANSACTION and ListFind is case-
sensitive. You get the point. To make it work I just changed ListFind
to ListFindNoCase (exists both in Adobe ColdFusion and Reactor).

Before: <cfset fieldList = ListDeleteAt(fieldList, ListFind(fieldList,
"useTransaction")) />

After: <cfset fieldList = ListDeleteAt(fieldList, ListFindNoCase
(fieldList, "useTransaction")) />

By changing this, I got everything to work 100% and my app to be fully
migrated to Railo. Job concluded :)

PS: I've used Railo 3.1.0.022 and reactor trunk-snapshot-2009-02-17-
r451 [the error still exists in the latest version])

[Tom Chiverton]

On Jul 21, 5:37 pm, Pedro Martins <martins.ped...@gmail.com> wrote:
> Before: <cfset fieldList = ListDeleteAt(fieldList, ListFind(fieldList,
> "useTransaction")) />
> After: <cfset fieldList = ListDeleteAt(fieldList, ListFindNoCase
> (fieldList, "useTransaction")) />

I've committed this fix to Reactor.
Please double check it works without changes with an updated build,
r457 or greater.

Tom
Lead Developer

[Pedro Martins]

I've updated to r459 and it all works fine. Thank you Tom for the fast
action.