Kathey Marsden <[EMAIL PROTECTED]> writes:
> > > > > Another thing I would try is paring down the query to make it as small > > as possible while still reproducing the problem. > > > > > Aye, there's the rub. In general with these byte code generation > problems it is the size of the query that is the problem. We are > dealing with strict JVM specification limits on things like method > sizes. So, we split methods into smaller methods and then we have too > many constants. Robbing Peter to pay Paul only works for so long. > > I create a java class with 30,000 constants of the form: int i1= 1,i2= 1,i3= 1,i4= 1,i5= 1,i6= 1,i7= 1,i8= 1,i9= 1,i10= 1; Java 1.3.1 compiles it ok but jad 1.5.7g gives an error when trying to decompile it. A dialog box titled 'Program Error' with 'jad.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created.' Couldn't find anything in the JVM spec about a limit on constants
