[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1367) warn level log "this operation breaks ==" may be disturbing

[Ed Shirey (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28399 ] 

Ed Shirey commented on HHH-1367:
--------------------------------

Noticed when attempting to deploy this that the class name in the note above does not correspond to the class name in the current distribution.

The correct logger name is:

"org.hibernate.engine.StatefulPersistenceContext.ProxyWarnLog"

Note the "Persistence" instead of "Persistent".  This is easily identified with some basic troubleshooting, but thought I'd try and save someone the 15 minutes.



> warn level log "this operation breaks ==" may be disturbing
> -----------------------------------------------------------
>
>                 Key: HHH-1367
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1367
>             Project: Hibernate3
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1
>         Environment: 3.1, oracle 9
>            Reporter: Peter Mutsaers
>            Assignee: Steve Ebersole
>            Priority: Minor
>             Fix For: 3.1.2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira