Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Widgetset does not contain implementation
I have just upgraded the project to use latest vaadin version 6
After changing the vaadin version to 6.8.17 -
I tried recompiling the Widgetset
I could see the files generated with the latest timestamp under - the project/../src/main/webapp/VAADIN/widgetsets
Cleared browser cache,
Restarted the jetty
But when the webpage which uses the widgetset loads, the browser is throwing the error -
Widgetset does not contain implementation XXXXX heck its @ClientWidget mapping, widgetsets GWT module description file and re-compile your widgetset. In case you have downloaded a vaadin add-on package, you might want to refer to add-on instructions. Unrendered UIDL:
Did you tried vaadin:compile instead of gwt:compile ?
Usually vaadin maven plugin should have same version as vaadin framework. Try to set version to 6.8.17 and then vaadin:compile again
Vaadin maven plugin does not have version 6.8.17
Sorry, my mistake. I've wrong read 6.8.17 as 7.6.8
Any other suggestions please?
I guess you have already tried to delete the whole src/main/webapp/VAADIN/widgetsets directory.
Do you use some addon from directory that could be incompatible with the new vaadin version?
Does the widgetset compilation give some kind of error or warnings?
Yes, I deleted the whole src/main/webapp/VAADIN/widgetsets directory and compiled- gwt-compile & vaadin:update-widgetset
I had attached gwt-compile console log.
Though the browser shows Widgetset does not contain implementation error...
Widgetset component works fine in the UI...
I am really confused...
I had restarted my machine, browser etc., to clear out any cache issues...
I'm sorry, I'm not able to reproduce your error.
Have you tried to use version 1.0.2 of vaadin-maven-plugin?
I've got dependency errors runnig 1.0.1
The goal vaadin:update-widgetset scan the classpath to find available widgetsets and then updates the .gwt.xml file.
Seems like that your own widgetset is not fount on classpath; according to the log you posted also the MaskedTextField addon seems not to be on classpath.
BTW, if update-widgetset is not configured to automatically run you should invoke it before gwt:compile
mvn clean compile vaadin:update-widgetset gwt:compile package jetty:run
Yes, the two goals will run automatically on the default phase they are bound.
To add addons on classpath simply add they as dependencies in pom file;
<dependencies> ... <dependency> <groupId>org.vaadin.addons</groupId> <artifactId>maskedtextfield</artifactId> <version>0.1.1</version> </dependency> ... </dependencies>
When using addons from vaadin directory also make sure you added the repository configuration
<repositories> ... <repository> <id>vaadin-addons</id> <url>http://maven.vaadin.com/vaadin-addons</url> </repository> --- </repositories>
Can you please post the output of mvn vaadin:update-widgetset ?
So seems like your XXXX addon is not found during scan.
Please, forgive the silly question: is the MANIFEST file of your addon correctly filled with vaadin entries?
Vaadin-Package-Version: 1 Vaadin-Widgetsets: com.package.AddonWidgetset ...
All seem ok, I can't figure out wath is happening.
Did you tried yo use -X flag when launching vaadin:update-widgetset or gwt:compile? Maybe this can give some additional information
mvn -X vaadin:update-widgetset