You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have two request scoped beans who reference each other when I attempt to load one of those beans I get an OutOfMemoryException because of an infinite loop.
As outlined in #7379, I have already added a check that throws a corresponding exception instead of the endless loop. This is already in CVS and should make it into the next nightly snapshot.
Sounds good to me thanks for the clarification.....sorry about the extra bug report I wasn't sure if the other one was being ignored or not because it was targeted towards custom scopes and not request or session scopes. :) Anyway, thanks.
Fixed in that a proper exception is thrown instead of an endless loop now.
I'll still keep #7379 open for the time being, since the issue of whether circular references should be supported for non-singletons has been explicitly raised there.
Mike Youngstrom opened SPR-2767 and commented
If I have two request scoped beans who reference each other when I attempt to load one of those beans I get an OutOfMemoryException because of an infinite loop.
Example:
<bean name="someBean" scope="request">
<property name="someOtherBean" ref="someOtherBean"/>
</bean>
<bean name="someOtherBean" scope="request">
<property name="someBean" ref="someBean"/>
</bean>
Even if circular references of non singleton scoped beans is not supported we should probably not have an infinite loop if it's possible to avoid.
Mike
Affects: 2.0 final
Issue Links:
The text was updated successfully, but these errors were encountered: