
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
3.1, oracle 9
|
|
|
The ref. manual 19.1.3 warns that a proxy may break ==. This is fine and understood, however the org.hibernate.engine.StatefulPersistenceContext class emits a commons-logging warning for this.
We have such a case in productive code, we know it may break == and understand the consequences. However it is irritating that this warning is generated at runtime.
The code which emits this warning is executed very often (in a batch process). We do not want to generally disable the warning log level, but we don't want our logfiles to get filled with this warning either.
Since this class only generates this warning log (no other warn() case) we can disable the warn level for the class for now, as a work around.
IMHO a case that may be normal (even if you have to take care) should not continue to generate such warnings. It is not a case we can avoid, we have to access the class once as superclass, and later in the same session as the subclass.
|
|
Description
|
The ref. manual 19.1.3 warns that a proxy may break ==. This is fine and understood, however the org.hibernate.engine.StatefulPersistenceContext class emits a commons-logging warning for this.
We have such a case in productive code, we know it may break == and understand the consequences. However it is irritating that this warning is generated at runtime.
The code which emits this warning is executed very often (in a batch process). We do not want to generally disable the warning log level, but we don't want our logfiles to get filled with this warning either.
Since this class only generates this warning log (no other warn() case) we can disable the warn level for the class for now, as a work around.
IMHO a case that may be normal (even if you have to take care) should not continue to generate such warnings. It is not a case we can avoid, we have to access the class once as superclass, and later in the same session as the subclass.
|
Show » |
|