Community
Participate
Working Groups
The JREContainerInitializer has a hack to avoid a stack overflow (which is a bug in JCORE). This hack should be removed once the JCORE bug is fixed.
Why do you think setting a container to null is a good thing to do ? What are you trying to achieve ?
I found that if I did not set a container to null, then the old value was used for the container (which referred to a non-existant JRE). I wanted to clear the binding so it was unbound.
Fixed.
Please verify, Darin (S).
Verified code.