[jboss-as7-dev] FYI, a new version of Javassist will soon be available which will have a fix for JASSIST-163 (impacts Weld, jbossws-native-core, scannotation, slf4j, Hibernate)...

[Scott Marlow]

After 3.1.17 of Javassist is released and testing looks good, we can 
look at AS7-5127 which is about upgrading javassist in as7 to improve 
performance (as long as the new javassist doesn't break anything). 
Obviously, if Javassist 3.1.17 breaks something, we will not be able to 
upgrade.

I took a look at which AS7 modules (statically) depend on javassist and 
the list is:

1. Weld

2. jbossws-native-core

3. scannotation

4. slf4j

5. Hibernate

I'm testing Hibernate with the new javassist but don't know how to test 
(1), (2), (3), (4) above.  Is there anything else that we need to try 
besides the AS7 testsuite to gain confidence that we can upgrade to 
javassist 3.1.17 (after its released soon)?

I built trunk of javassist locally and caught one minor failure with the 
Hibernate test suite (see yesterdays comments in JASSIST-163).  I'm 
built AS7 with the updated hibernate/javassist jars and passed the AS7 
testsuite.

If anyone wants to do additional testing with the javassist trunk, let 
me know and I'll ask for more time to do testing before 3.1.17 is 
released.  Or others could also coordinate through JASSIST-163.

Scott