If you are using Vaadin Charts, that means you have a custom widgetset, so you cannot use the “default”
Vaadin7Widgetset . I assume you have a module descriptor, say
com/example/Widgetset.gwt.xml file. there, you should have at least:
When compiling with Maven this should be done automatically. You should also have the following in you UI implementation:
@Widgetset("
com.example.Widgetset ")
public class YourUI extends UI { … }
I tested it, and it works For completeness, here’s the full dependencies section of the pom.xml file I used:
I thought the dark days of XYZWidgetset.gwt.xml have ended since vaadin 7.7 - I for sure was glad having the configuration simplified. Too bad I had to reintroduce it again, is this temporary ?
Anyways I managed to have everything up and running according to your instructions.
However… everything is fine when using 8.0.0.beta1, but when I switch to 8.0-SNAPSHOT (which is what I REALLY want), I get an
OutOfMemoryError :
[INFO]
Compiling module MyAppWidgetset
[ERROR]
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
[ERROR]
at org.eclipse.jdt.internal.compiler.util.HashtableOfObject.<init>(HashtableOfObject.java:38)
[ERROR]
at org.eclipse.jdt.internal.compiler.codegen.ConstantPool.<init>(ConstantPool.java:309)
[ERROR]
at org.eclipse.jdt.internal.compiler.ClassFile.<init>(ClassFile.java:271)
[ERROR]
at org.eclipse.jdt.internal.compiler.ClassFilePool.acquire(ClassFilePool.java:45)
[ERROR]
at org.eclipse.jdt.internal.compiler.ClassFile.getNewInstance(ClassFile.java:259)
[ERROR]
at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.generateCode(TypeDeclaration.java:537)
[ERROR]
at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.generateCode(TypeDeclaration.java:636)
[ERROR]
at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.generateCode(CompilationUnitDeclaration.java:371)
[ERROR]
at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:872)
I’ll try to increase memory available for maven using MAVEN_OPTS and post back, but anyway this not good news.
Hi,
the widgetset compilation runs in a forked process. To set memory allocation params try to use
-Dgwt.extraJvmArgs=“-Xms512m -Xmx1512m” on command line or
extraJvmArgs property in plugin configuration.
I tested the jpacontainer-addressbook-demo with vaadin 8.1.1 and connat make it run.
Thanks to Alejandro’s hints I could fix the problems.
Now it’s runnung.
One small question: When we are using a custom Widgetset, do we still need the vaadin-compatibility-client-compiled? We currently have both the client and client-compiled in our pom.xml.
[/font]
vaadin
-compatibility-client-compiled when using a custom widgetset. However you must inherit
com.vaadin.v7.Vaadin7WidgetSet in your
.gwt.xml module descriptor. See my previous answer for an example.