2012/8/16 Jess Holle <je...@ptc.com>: > It appears that when one installs the groovy-all-2.0.1-indy.jar in a Tomcat > web app, BCEL chokes on the Java 7 specific byte-code therein ala > > org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte > tag in constant pool: 15 > at > org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:131) > at > org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:60) > at > org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:209) > at > org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:119) > at > org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2066) > ... > > Is there an update planned to make org.apache.tomcat.util.bcel savvy to Java > 7 or replace it with ASM (which is fully Java 7 savvy)? [Please!]
BCEL is now being developed at Apache Commons. If one contributes a patch there, I think it will make its way into Tomcat as well. I do not think that anyone would bother replacing the annotation scanning code with ASM one. http://commons.apache.org/bcel/ > > Until then, can I completely exclude this jar from annotation scanning? > 1. The property in catalina.properties, as mentioned by Christopher. 2. Annotations would not be scanned if your web.xml has metadata-complete="true". Also, if I understand the feature described by BZ 53619, one should also add an empty <absolute-ordering/> to web.xml. https://issues.apache.org/bugzilla/show_bug.cgi?id=53619 Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
