Vaadin Widget Compile Problem

[mehmet tasar, modifié il y a 11 années.]

Hello All,
I am getting exception below while compiling vaadin widget with eclipse.

Starting GWT compiler
Compiling module com.psp.defaultWidgetset.PSP_portletWidgetset
[ERROR] Unexpected internal compiler error
java.lang.NoSuchFieldError: warningThreshold
	at com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:413)
	at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.<init>(JdtCompiler.java:228)
	at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:717)
	at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:248)
	at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:463)
	at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:388)
	at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:373)
	at com.google.gwt.dev.Precompile.precompile(Precompile.java:246)
	at com.google.gwt.dev.Precompile.precompile(Precompile.java:229)
	at com.google.gwt.dev.Precompile.precompile(Precompile.java:141)
	at com.google.gwt.dev.Compiler.run(Compiler.java:232)
	at com.google.gwt.dev.Compiler.run(Compiler.java:198)
	at com.google.gwt.dev.Compiler$1.run(Compiler.java:170)
	at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:88)
	at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:82)
	at com.google.gwt.dev.Compiler.main(Compiler.java:177)
	at com.vaadin.tools.WidgetsetCompiler$1.run(WidgetsetCompiler.java:80)
	at java.lang.Thread.run(Thread.java:619)
Widgetset compilation failed</init>

I have added all necessary jars to classpath. Do you have any idea about this.NoSuchFieldError: warningThreshold error ?

[David H Nebinger, modifié il y a 11 années.]

What jdk/version are you using? What version of Vaadin? Are you using the Vaadin control panel to compile the widgetset?

[mehmet tasar, modifié il y a 11 années.]

What jdk/version are you using?
-jdk 7
What version of Vaadin?
-Vaadin 7 I have switched from 6 to 7.
Are you using the Vaadin control panel to compile the widgetset?
No I do not use vaadin control panel; only try with eclipse vaadin plugin.

I have tablefilter and confirm dialog addons in my classpath..

[David H Nebinger, modifié il y a 11 années.]

Okay, well a couple of things then:

1. Liferay is only compatible w/ JDK 6, and primarily oracle's version of the JDK. You really should stick with what you're using for the portal since that's your target environment.

2. Vaadin 7 is still pretty new, and there are still some issues using it under Liferay. I have a couple of bugs open on it myself. IE10 is currently unsupported by V7 too (I think they're working on fixing it in 7.0.5/7.1.0). Personally I'd advise folks to stick with V6 at least until the dust settles and the significant bugs are resolved.

3. To use Vaadin in Liferay, you really must use the Vaadin Control Panel. Vaadin in the portal uses a shared widgetset directory from /webapps/ROOT/html/VAADIN, and will not use a local widgetset provided with your portlet. The VCP will help you compile the widgetset on the portal, a step you'll need to do for your Vaadin portlets to work anyway. The V7 control panel is currently only a release candidate, which is yet another reason to stay with Vaadin 6 in the short term.

A couple of google results that may help:

https://code.google.com/p/google-web-toolkit/issues/detail?id=4479
http://stackoverflow.com/questions/7594099/gwt-spring-hosted-mode-not-working
https://groups.google.com/forum/#!topic/google-web-toolkit/t8qm22isWsg
http://stackoverflow.com/questions/5099249/gwt-wont-deploy-to-google

[mehmet tasar, modifié il y a 11 années.]

David,
This information is very helpful.

also I have two question.
1) Which jar files should be exist in portlet classpath for vaadin 7?

2) Can you write a sample web.xml file for vaadin 7?

thanks for vaadin supports to community..

[David H Nebinger, modifié il y a 11 années.]

I would recommend avoiding V7 at the moment. The latest release, 7.0.4, is not compatible with IE10 (anyone using automatic updates has it already). Plus there are some bugs when using it in Liferay (I opened two, http://dev.vaadin.com/ticket/11394 and http://dev.vaadin.com/ticket/11372, and commented on another http://dev.vaadin.com/ticket/10707.

The Vaadin 7 control panel (again, a requirement when using Vaadin in Liferay), is currently only a RC.

While some V7 addons have come in, there are still a bunch that are only compatible w/ V6. If you have a set of addons you plan on using, you should check the directory to ensure there are V7 versions available before making the change.

To answer your questions:

1 - you need vaadin-server, vaadin-shared, vaadin-shared-deps, and jsoup.

2 - nothing is needed in web.xml for a V7 portlet. All is done in the portlet.xml file.

[mehmet tasar, modifié il y a 11 années.]

Version 7.1 will be released in April 2013 with.
What is your foresight time for the stable Vaadin 7 version in liferay?

We want to switch from alloy to vaadin in long term. (maybe six month)

Is it a mistake to continue with vaadin 7?
or do you recommend to start vaadin 6?

[David H Nebinger, modifié il y a 11 années.]

I'm hoping V7 will be stable enough in Liferay in 6 mos, but in the mean time V6 is rock-solid. V6 is still being supported (well into next year).

The migration path from V6 to V7 is not too difficult (note it depends upon what your portlet is doing). We are still using V6 for development and will continue w/ V6 until all of our addons have been either migrated to V7 or V7-compatible alternatives are available.

I guess I'd say if you were going to be deploying any time soon, stick with V6. V7 development should at least wait until the V7CP is done and available, as that is a key part of using Vaadin in Liferay. But 6 mos out, the dust should be settled, all of the issues identified (and hopefully resolved), the V7CP should be gold, addons should be available, and migration instructions should abound...

That said, I'm not connected with either entity (Liferay or Vaadin), so they may weigh in with differing opinions from my own...

[Jack Bakker, modifié il y a 11 années.]

Vaadin v6.8.10 is stable in Liferay including for IE10native (from my limited tests) ; but like many I am also looking forward to features of Vaadin v7.1, Liferay v6.2

But as the famous cartoonist Kliban wrote: Never Eat Anything Bigger Than Your Head

[David Morris, modifié il y a 10 années.]

See https://vaadin.com/forum#!/thread/3902907