Deploying Vaddin into Existing Web Application

We have a working web application to which we want to add a Vaadin application. We are looking into this case in order to understand what exactly happens on the server side. We are less interested in solutions that don’t provide with the insight we are looking for.

  1. We updated the web.xml of our working web application with the mapping for Vaadin servlet:
<?xml version="1.0" encoding="UTF-8"?> Gym Tracker index.html index.htm index.jsp default.html default.htm default.jsp /WEB-INF/firstTag.tld /WEB-INF/firstTag.tld /WEB-INF/secondTag.tld /WEB-INF/secondTag.tld Gym_tracker_vaadin Application com.vaadin.terminal.gwt.server.ApplicationServlet Vaadin application class to start application com.example.gym_tracker_vaadin.Gym_tracker_vaadinApplication Gym_tracker_vaadin Application /VAADIN/*
  1. It is clear that the server side finds the Vaadin servlet. When you try to browse our web application at http://oferhit.softwarelabs.org/VAADIN you get an error message that indicates about that.

  2. We wrote a small JSP document in order to verify that the com.example.gym_tracker_vaadin.Gym_tracker_vaadinApplication can be found. We wrote the following JSP document:

<%
com.example.gym_tracker_vaadin.Gym_tracker_vaadinApplication x = new com.example.gym_tracker_vaadin.Gym_tracker_vaadinApplication();
%>
You can find it at http://oferhit.softwarelabs.org/gogo.jsp. If you try to browse it you will get an empty page. This is an indication for the fact that our com.example.gym_tracker_vaadin.Gym_tracker_vaadinApplication class is available.

  1. Just for the records, the Vaadin jar file was placed within the lib folder (sub folder within WEB-INF).

I will be very glad to get any insight about this strange behavior.

Thanks in advance,

Ofer.

Hi, trying to map your application to /VAADIN/* won’t work as an URL for your application, since It serves the static resources related to Vaadin (themes and such). Instead, add another servlet mapping with a URL pattern other than /VAADIN/, for instance /Myapp/. Then try to navigate to http://url/Myapp/ and see if it helps.