| Reporter |
Evgeniy Schepotiev (zeckson)
|
|---|---|
| Created | Jun 19, 2013 4:38:33 PM |
| Updated | Jun 19, 2013 5:13:20 PM |
| Priority | Critical |
| Type | Bug |
| State | Open |
| Assignee | Evgeniy Schepotiev (zeckson) |
| Subsystem | No subsystem |
| Fix versions | Next EAP |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
Here is scope destruction callback registration.
It called in direct order on bean initialization.
But on scope close we should call in reverse order or even better check dependent beans:
It called in direct order on bean initialization.
void registerDestructionCallback(String name, Runnable callback) {
if (log.isDebugEnabled()){
log.debug("Register destructor callback for bean " + name);
}
destructionCallbacks.put(name, callback);
}
But on scope close we should call in reverse order or even better check dependent beans:
void destroy() {
for (final String name : destructionCallbacks.keySet()) {
final Runnable callback = destructionCallbacks.get(name);
callback.run();
}
}