Run Vaadin example app on Wildfly

General
1

Hi,

I’m new to vaadin and would like to run my apps on a wildfly 10 server.

I’ve used this tutorial

https://www.youtube.com/watch?v=sMGHSK_97NI (Vaadin tutorial: Creating a Project from an Archetype)

to get started.

The project runs on tomcat, but not on wildfly. I think this can be related to the following loggings:

15:05:44,750 WARN [org.jboss.as.server.deployment]
(MSC service thread 1-6) JBAS015960: Class Path entry yuicompressor-2.4.8.jar in /C:/Users/CHILI-WIN7/wildfly-8.2.1.Final/standalone/deployments/app-0.0.1-SNAPSHOT.war/WEB-INF/lib/vaadin-sass-compiler-0.9.13.jar does not point to a valid jar for a Class-Path reference.
15:05:44,750 WARN [org.jboss.as.server.deployment]
(MSC service thread 1-6) JBAS015960: Class Path entry js-1.7R2.jar in /C:/Users/CHILI-WIN7/wildfly-8.2.1.Final/standalone/deployments/app-0.0.1-SNAPSHOT.war/WEB-INF/lib/vaadin-sass-compiler-0.9.13.jar does not point to a valid jar for a Class-Path reference.

Does anyone experienced the same problem and know how to solve this?

Thanks,

Regards Klaus

2

I haven’t had such issues with Wildfly, which I use in Java EE experiments regurarly (although I use Wildfly 10). Vaadin should be compatible with Wildfly versions 8 to 10. Why you use 8 series? Also have you checked that when deployed those files really go in right places. E.g. if file /C:/Users/CHILI-WIN7/wildfly-8.2.1.Final/standalone/deployments/app-0.0.1-SNAPSHOT.war/WEB-INF/lib/vaadin-sass-compiler-0.9.13.jar is not there, you have something wrong in war package process. When running under Tomcat in IDE that is done differently. That may explain things.

3

HI, thanks for your message - I’ve just tried it on different wildfly versions.

The point is, that when my eclipse ee project is called:‘firstvaadin’ the app is available on wildfly under

http://localhost:8080/firstvaadin-0.0.1-SNAPSHOT/

in comparison to tomcat or jetty:run - command where it is available under

http://localhost:8080/firstvaadin

4

Hi,

its warnings, so you application should run. Ifs like in OSGI, its going and checking the dependencies of each dependency and warn you if some lib is not accessible.