[ https://jira.jboss.org/browse/JBREFLECT-127?page=com.atlassian.jira.plugi... ] Kabir Khan commented on JBREFLECT-127: -------------------------------------- On 11 Jun 2010, at 15:54, Carlo de Wolf wrote: It's working. :-) One System.out too many though: ---> TypeInfoFactory: org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory@12884e0 Carlo On 06/11/2010 03:26 PM, Kabir Khan wrote: I've upgraded AS trunk to use these versions. Let me know if that fixes things On 11 Jun 2010, at 14:00, Kabir Khan wrote: I have released jboss-reflect 2.2.0.Alpha6 and it's dependency javassist 3.12.1.GA (which is what I guess you meant by "not compatible". I'm building and running the aop + smoke tests, before I commit the upgrades. This was a problem in javassist when "comparing" the classes methods to see if anything has been added (there is support in JavassistTypeInfo for adding members), so it should hopefully not happen with the introspection implementation. On 11 Jun 2010, at 13:23, Kabir Khan wrote: The javassist and introspection implementations are more or less independent On 11 Jun 2010, at 13:22, Carlo de Wolf wrote: Unless it also changed the way reflect handles undefined classes the actual bug might be in a piece of higher logic. Carlo On 06/11/2010 01:58 PM, Kabir Khan wrote: I'll do a jboss-reflect release that reverts back to using introspection. Using javassist in the last release was a mistake On 11 Jun 2010, at 12:49, Carlo de Wolf wrote: jboss-reflect/trunk is not compatible with AS/trunk, so I can't do an easy patch for JBREFLECT-127. Carlo On 06/11/2010 01:48 PM, Carlo de Wolf wrote: The client launcher won't launch anymore because org.jboss.ejb3.InjectionContainer.resolveEjbContainer returns org.jboss.ejb3.Container which has injectBeanContext(BeanContext) while BeanContext is not available to the client. https://jira.jboss.org/browse/JBCTS-1020 The net effect is that TCK 6 is close to completely down. Carlo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira