Thanks David, I saw new code. Early, I wrote code from javap applied to old
code.
I am mistaken, this is not a compiler bug.
djencks wrote:
>
> I'm a little confused. What code did you apply javap to? I dont
> think I pushed a copy of the newly revised code to any repos so you'd
> have to build it yourself.
>
> The new code looks like this:
>
> public boolean equals(Object o) {
> if (this == o) return true;
> if (o == null || getClass() != o.getClass()) return false;
>
> SubjectCRIKey that = (SubjectCRIKey) o;
>
> if (hashcode != that.hashcode) return false;
> if (cri != null ? !cri.equals(that.cri) : that.cri !=
> null) return false;
> if (subject != null ? !subject.equals(that.subject) :
> that.subject != null) return false;
>
> return true;
> }
>
>
> I can believe the old code resembled your deconstruction below with
> the addition of a "return".
>
> thanks
> david jencks
>
>
--
View this message in context:
http://www.nabble.com/NullPointerException-MultiPoolConnectionInterceptor%24SubjectCRIKey.equals-tp23634940s134p23649541.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
