This is absolutely a bug in Railo. Changing this behavior can introduce *serious* and subtle thread safety bugs in code that would otherwise be thread safe in Adobe CF.
Knowing this I'd be really really hesitant to deploy any application on Railo. - Elliott On May 20, 6:43 pm, Luis Majano <[email protected]> wrote: > After seeing that post, I could not reply to it, so I am adding my > answer here > > Those issues on the recurssion are related with the Array by reference > deal. Basically, Adobe CF handles arrays by value and Railo by > reference. A topic I don't want to get into because I think arrays by > value are basically STUPID. > > Anyways, you can have a workaround by using "lazy=true" on your > relationships so the recursion stops. However, the real solution is > to add the compatibility argument to the transfer core when recursing > with arrays. > > Basically when passing arguments by value, you need to add the > following metdata to the argument tag: passby="value" > > <cfargument name="myArray" type="Array" passby="value" /> > > If you do that, then you can go back to caveman mode and use arrays by > value. > > Luis --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
