Noticed that if a TypeChecker is ever created for java.lang.Object that it will throw a NullPointerException if TypeChecker.getSuperName(..) is ever called.
Found this out 'cause I'm trying to create an implementation for hashCode() in an object that directly subclasses java.lang.Object. The body I'm creating for the overriding definition of hashCode invokes super.hashCode(). The javassist compiler is choking because a TypeChecker for java.lang.Object is created and TyperChecker.atKeyword(..) is finding the "super" keyword but somehow the "thisClass" attributte is set to java.lang.Object. This utlimately leads to NullPointerException. Seems like "thisClass" should not be java.lang.Object. Is there something I'm missing here? In any case, something more polite than NullPointerException might be considered. Thanks, Matt View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884571#3884571 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884571 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
