Running normally, the IdP’s on-exception code in the flows is working as before, but the testbed under Eclipse is acting up. Any time the LogRuntimeException action-state runs, it ends up spiraling into a stack overflow because the expression logic seems to be unable to load any classes. It seemed to raise an Access exception at one point. I thought it was logging-related, but various tests suggest that’s not involved.
Will try seeing if only T() expressions are breaking or if anything there does the same thing.
I’m not inclined to go crazy trying to fix this if it’s confined to the testbed for now.
Running normally, the IdP’s on-exception code in the flows is working as before, but the testbed under Eclipse is acting up. Any time the LogRuntimeException action-state runs, it ends up spiraling into a stack overflow because the expression logic seems to be unable to load any classes. It seemed to raise an Access exception at one point. I thought it was logging-related, but various tests suggest that’s not involved.
Will try seeing if only T() expressions are breaking or if anything there does the same thing.
I’m not inclined to go crazy trying to fix this if it’s confined to the testbed for now.