My first test with vaadin 7

Vaadin 6 / 7 / 8
1

Hi!

I’m trying too setup a new project with Vaadin 7 beta 4.

I’m using m2e (maven for eclipse).

I created an new application using:

archetype:generate
archetypeGroupId=com.vaadin
archetypeArtifactId=vaadin-archetype-application
archetypeVersion=7.0.0.beta4

After this, I created a server config with WTP and Tomcat7.

Now, running it and accessing by http://localhost:8080/TestVaadin7 I got this error:

JAVA CONSOLE:
INFO: Requested resource
[/VAADIN/widgetsets/foo.AppWidgetSet/foo.AppWidgetSet.nocache.js] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder.

JAVASCRIPT console:
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:8080/TestVaadin7/VAADIN/widgetsets/foo.AppWidgetSet/foo.AppWidgetSet.nocache.js?1350478064646

What am I doing wrong?

2

I have the same problem using the maven archetype for Vaadin7 Beta 4. Any Help?

Thanks
Martin

3

Hi

I found a solution how it works. I replaced the jetty plugin with the tomcat plugin (Because i know tomcat better) and used the goal
tomcat:run
 to start Vaadin. Then the Vaadin GWT-compiler kicked in and the widgetset was available.

To add the tomcat plugin use:

		<plugin>
			<groupId>org.apache.tomcat.maven</groupId>
			<artifactId>tomcat7-maven-plugin</artifactId>
			<version>2.0</version>
		</plugin>

Maybe it is also possible to run the GWT-Compiler with its own goal
vaadin:compile
 before running jetty. I do not know the reason why the GWT-compiler does not run automatic with the jetty plugin.

Regards
Martin

4

Look at
this
 post.

I removed this part from web.xml and it worked:

<init-param>
   <description>Application widgetset</description>
   <param-name>widgetset</param-name>
   <param-value>com.X.AppWidgetSet</param-value>
</init-param>
5

Am also struck into a similar problem. Removing the widgetset param web.xml or @VaadinServletConfiguration though fix this js loader issue this brings in another problem that complains widgetset needs to be compiled again.

6

You need to compile the code before starting jetty.

So try:

mvn install
(will take a while and might show some errors, but should normally end successfuly)

And only then, run jetty:

mvn jetty:run