Yes, it helps to break it up further....
I guess the JVM limits the number of bytes in the actual block, not the
number of function calls making it pretty diffucult to fix.
I think that it's probably a better bet to break it up more, since I
don't think there is any performance hit by breaking it into more method
calls.
For my particular needs, I seem to have to limit it to about 900-1000
calls...so i end up with 4 static blocks
MD
Kohsuke Kawaguchi wrote:
>>I'm pretty sure this has shown up on the list before, so i'm
>>disappointed that it wasn't fixed in the 1.0 version. When using large
>>schemas, JAXB creates a large static block in the ObjectFactory class;
>>one that is too large to be executed by the JVM.
>>
>>
>
>That must be my fault. I think I did added code to split it to smaller
>chunks. But apparently that wasn't enough. Can I get access to the
>schema you use?
>
>Does it solve the problem if I further reduce the size of each
>initialization method?
>
>
>
>
>>My solution has been to break up the static block into 2 static methods.
>>But I have to do this each time i regenerate my classes..
>>
>>can we expect to see a fix to this?
>>
>>
>
>I'd like to fix it, but that doesn't guarantee that I can or I will.
>
>regards,
>--
>Kohsuke KAWAGUCHI 408-276-7063 (x17063)
>Sun Microsystems kohsuke.kawaguchi_at_sun.com
>
>