SetNextEvent -- Persisting RC causes infinite loop

Has there been any other reports or progress on this issue?

We’re experiencing the same when moving from 3.5.0 to 3.5.2 when using setNextEvent() with persistStruct=rc

Is it inflating the same event then? I say remove it before flashing the entire rc.

signature0.jpg

Luis F. Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com

ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com

Social: twitter.com/lmajano facebook.com/lmajano

I’m not sure what you’re asking me Luis?

My use case is a form action event when the form fails server-side validation and the handler is passing back to the form view the submitted form values for redisplay.

My concern is that that everything is working fine under 3.5.0 but some core change has caused this infinite loop in 3.5.2

So what I think is happening is that the flash of the full rc flashes the event variable.

Upon relocation it overrides the incoming one.

That’s why I suggest Not flashing the entire rc. Or remove the “event” or exclude it.

Okay, so I tried adding a…

structDelete(rc, “event”);

…before my setnextEvent() but that didn’t seem to help. Next I tried using persist=“fieldname1,fieldname2” which worked but is a maintenance nightmare!

But then I saw that you supply “formCollectionsList” in the rc scope which is great for me as my form fieldnames are strucutured like “course.code”, “course.title” and “stage.name” etc.

So now I have replaced…

persistStruct=rc

…with…

persist=rc.formCollectionsList

…and all seems good.

I’ve some more testing to do but what do you think?

Yea, I am very perplexed at why it would do that.

signature0.jpg

Luis F. Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com

ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com

Social: twitter.com/lmajano facebook.com/lmajano

Me too.

The only other info I can offer is that I’m working on Railo 3.3.4.003 and I’m using SES within ColdBox but not at the web server level.

I say use some logbox logging to trace this