[
https://issues.apache.org/jira/browse/OPENJPA-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757945#action_12757945
]
Tim McConnell commented on OPENJPA-1319:
----------------------------------------
Hi Mike, these problems can be easily reproduced in the Eclipse debugger
without adding any diagnostics to the OpenJPA code, which is how I initially
uncovered the problem. When you set a breakpoint and interrogate an instance of
one of these classes, Eclipse will invoke the toString() method for that class
on your behalf, which will in turn invoke the hashcode() method which may cause
a NPE based on the state of the object when it is interrogated. At least for me
I find this behavior to be extremely distracting especially when I'm trying to
find and fix other problems.
I'm only adding diagnostic info code for the sake of efficiency to quickly
uncover all these problems since it emulates what will happen in Eclipse (i.e.,
toString() invoking hashcode()), and is much faster for me. If you'd prefer
actual testcases I can provide them as well, but it will take me much longer to
reproduce and fix them. Thanks
> EntityManagerImpl
> -----------------
>
> Key: OPENJPA-1319
> URL: https://issues.apache.org/jira/browse/OPENJPA-1319
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 1.0.3, 1.1.0, 1.2.1, 1.3.0, 2.0.0-M2
> Reporter: Tim McConnell
> Assignee: Donald Woods
> Fix For: 1.3.0, 2.0.0-M3
>
> Attachments: OPENJPA-1319.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
