Ales, After taking a look at JBoss Reflection implementation, I have a few questions: - Why aren't the classes JavassistField, JavassistConstructor, JavassistMethod and JavassistReflectionFactory package-protected? Those names can be easily mistaken with JavassistFieldInfo, JavassistConstructorInfo, etc and they are only used inside their own package. -What is MutableMethodInfoCommand for? -At JavassistTypeInfo, what do the TODOS like the one below mean? //TODO: need to change the use of getType() here public boolean isCollection() { return Collection.class.isAssignableFrom(getType()); } I see that getType is deprecated. But what is the main idea behind this? - Are the Javassist Expression interfaces needed? I mean, from http://www.jboss.org/index.html?module=bb&op=viewtopic&t=148169&a..., It is clear they were created for JBoss AOP integration. And I also see that those interfaces were not even implemented. Is it that all, or there is another use case for those? Just trying to define the priority of filling in these blanks. Plus, I've seen a TODO with JBMICROCONT-132 at ValueConvertor class and this task was resolved in 2006. You left an open question on whether we should remove the support for value creation via constructor with one String parameter. Do you have an answer to this question? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236866#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...