cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Madu" <andrewm...@gmail.com>
Subject Re: Instruction INVOKEVIRTUAL constraint violated
Date Tue, 21 Mar 2006 22:10:06 GMT
Hi Torsten,
thanks for your reply. I was just seeing what I could and couldn't do with
java flow classes. I stmbled across this one by accident to be honest. Like
you say, it should work!

Andrew

On 3/21/06, Torsten Curdt <tcurdt@apache.org> wrote:
>
>
> On 21.03.2006, at 20:26, Andrew Madu wrote:
>
> > Hi,
> > can someone please tell me why defining a class variable in a
> > javaflow class like so:
> >
> > public class Login extends AbstractContinuable
> > {
> >     static User userGlobal = new User();
> >     .........
> >
> >
> > would cause the following error to be generated?:
>
> Andrew, that's the BCEL code verifier that barfs on you.
> Obviously for no good reason. Since I don't think you
> are using trunk upgrading to a newer javaflow version
> is probably no option.
>
> A subtile code change might make a difference. You could
> try a bit ...but rather I would re-think your approach.
> Despite the fact it should work - are you sure that a
> static global user object is the right way to go?
>
> cheers
> --
> Torsten
>
>
>
>
>

Mime
View raw message