hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1934) logging NonUniqueObjectException and WrongClassException

[Holger H. (JIRA) <no...@at...>]

logging NonUniqueObjectException and WrongClassException
--------------------------------------------------------

         Key: HHH-1934
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934
     Project: Hibernate3
        Type: Improvement

  Components: core  
    Reporter: Holger Haag
    Priority: Trivial
 Attachments: hb.patch

Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions.

-- 
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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1934) logging NonUniqueObjectException and WrongClassException

[Max R. A. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=all ]
     
Max Rydahl Andersen closed HHH-1934:
------------------------------------

    Fix Version: 3.2.0.ga
     Resolution: Fixed

I applied the wrongclass patch, but the other one i decided not to do since
it requires calling "tostring" on the object which we would like to avoid (it could trigger more exceptions)



> logging NonUniqueObjectException and WrongClassException
> --------------------------------------------------------
>
>          Key: HHH-1934
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Holger Haag
>     Priority: Trivial
>      Fix For: 3.2.0.ga
>  Attachments: hb.patch
>
>
> Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions.

-- 
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1934) logging NonUniqueObjectException and WrongClassException

[Holger H. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=comments#action_23733 ] 

Holger Haag commented on HHH-1934:
----------------------------------

Thanks.  You're right about the toString() since anything can happen in there. What about removing the implicit toString() calls and only showing the the values of old.getClass().getCanonicalName() and entity.getClass().getCanonicalName() ?

> logging NonUniqueObjectException and WrongClassException
> --------------------------------------------------------
>
>          Key: HHH-1934
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Holger Haag
>     Priority: Trivial
>      Fix For: 3.2.0.ga
>  Attachments: hb.patch
>
>
> Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions.

-- 
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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1934) logging NonUniqueObjectException and WrongClassException

[Max R. A. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=comments#action_23734 ] 

Max Rydahl Andersen commented on HHH-1934:
------------------------------------------

there is also the issue of us logging and then throwing which we should also avoid.

Furthermore in 99% of the cases the class and (definitly the) id will be exactly the same and thus this line is only relevant if they are actually different.
And I would say that should actually never be able to happen....(they could of course be one subclass or the other, but its still very rare)

I'm not keen on adding that since i haven't seen it being an issue that isn't quicker/better solved with a debugger.



> logging NonUniqueObjectException and WrongClassException
> --------------------------------------------------------
>
>          Key: HHH-1934
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Holger Haag
>     Priority: Trivial
>      Fix For: 3.2.0.ga
>  Attachments: hb.patch
>
>
> Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions.

-- 
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