2012/8/18 Jess Holle :
> Until it is updated, Tomcat's annotation scanning will be broken for some
> Java 7 byte code. That's not really a tenable state long term.
>
I have filed an issue, as this really needs to be addressed before
Tomcat 8 is released.
https://issues.apache.org/bugzilla/show_b
On 8/17/2012 3:18 PM, Konstantin Kolinko wrote:
2012/8/16 Jess Holle :
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 i
2012/8/16 Jess Holle :
> 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.apac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jess,
On 8/16/12 12:19 PM, Jess Holle wrote:
> On 8/16/2012 11:14 AM, Pid * wrote:
>> On 16 Aug 2012, at 17:10, Jess Holle 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 s
On 8/16/2012 11:14 AM, Pid * wrote:
On 16 Aug 2012, at 17:10, Jess Holle 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
On 16 Aug 2012, at 17:10, Jess Holle 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
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.Co
