Because there are limitations with how the mc determines matching method signatures in the absence of an explicit signature declaration and jdk6 is returning reflection info in a different order for one, and this issue looks to be different handling of an implicitly referenced array class. Testing with jdk6 isn't a big priority currently, so if you want to drill into the issue and supply a patch that would be great. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037710#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...