Hi, I'd like to upgrade XBean in OpenEJB to its latest version for @ApplicationException extended handling (cf. Optional @ApplicationException inheritance http://issues.apache.org/jira/browse/OPENEJB-980), but missing asm-finder makes it hard. So I though I repackage asm in xbean-finder in XBean project with maven-shade-plugin. I actually did it and change all the asm-finder references to the new xbean-finder-asm-shaded module. I did change org.apache.openejb.asm package to its origin org.objectweb and added asm-3.1 to pom.xml as a hard dependency. OpenEJB built fine until the jpa-hibernate example was built and blew up due to asm conflicts - Hibernate uses 1.5.3 and OpenEJB does 3.1 (there's a known binary incompatibility between them).
I think there's nothing we can do about it other than to repackage asm and use it instead of org.objectweb. It was once with asm-finder, but it got removed. I wonder why? Shouldn't it be a regular OpenEJB module with a proper dependency mg,t so when we want to upgrade XBean it will boil down to updating pom (in its easiest case)? I'm ready to implement it unless it gets banned. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
