You can also turn off the validator by saying:
<canvas validate="false">
This will turn off the xml validator, which gets its knickers in a
knot when there are too many classes (it seems its stack depth goes
up with classes, and as you found you can increase the stack and get
by). The compiler is still pretty good job of reporting errors, but
it is possible you will slip some invalid xml by it.
On 2007-06-29, at 14:18 EDT, Jes Lefcourt wrote:
Of course, the second I give up and email the user group, I solve
my own problem...
Turned out that this error gets thrown due to a stack overflow. I
changed the Xss setting on my JVM and it went away.
I hope this saves someone some frustration...
- Jes
On Jun 29, 2007, at 12:05 PM, Jes Lefcourt wrote:
Hello,
I have an application with about 400 classes, and have reached a
point where, if I add any more classes, then when trying to
compile the program, I get the following errors:
base/basebutton.lzx:1:10: The validator had a fatal error, but
proceeding with compilation
base/basecomponent.lzx:1:10: The validator had a fatal error, but
proceeding with compilation
base/style.lzx:1:10: The validator had a fatal error, but
proceeding with compilation
...
This error occurs for every single class which gets included with
the application. I have written bigger OL programs than this in
the past, but only ones which were deployed in SOLO mode.
Unfortunately, this application uses the SOAP packages, so I
cannot deploy SOLO.
Since this seems like a memory issue, I tried increasing the
memory of my container to Xmx1024 / Xms512, but that has not helped.
Any suggestions?
Thanks!
- Jes
