tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jess Holle <je...@ptc.com>
Subject Re: Tomcat 7.0.29 vs. Groovy with Java 7
Date Thu, 16 Aug 2012 16:19:22 GMT
On 8/16/2012 11:14 AM, Pid * wrote:
> On 16 Aug 2012, at 17:10, Jess Holle <jessh@ptc.com> wrote:
>> 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!]
>>
>> Until then, can I completely exclude this jar from annotation scanning?
> Yes!
Sorry, but how?

--
Jess Holle


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message