spring-booted vaadin cannot use the non-root servlet path

[vaadin-bot]

Originally by ksaua on 2015-10-20 14:56:55 +0300

---

Using the base:

@SpringBootApplication
public class SpringBootTestApplication {

    public static void main(String[] args) {
        SpringApplication.run(SpringBootTestApplication.class, args);
    }

    @SpringUI
    public static class MyVaadinUI extends UI {
        @Override
        protected void init(VaadinRequest vaadinRequest) {
            setContent(new Label("Hello! I'm the root UI!"));
        }
    }
}

I see from the log:

2015-10-20 13:50:34.166  INFO 16180 --- [ost-startStop-1] c.v.s.b.i.VaadinServletConfiguration     : Servlet will be mapped to URLs [/vaadinServlet/*, /VAADIN/*]

However, if try to access it on http://localhost:8080/vaadinServlet/ I get

Failed to load the bootstrap javascript: ./VAADIN/vaadinBootstrap.js?v=7.5.5

This happens because the ServletForwardingController-hack contradicts the VaadinServletService#getStaticFileLocation usage of servletRequest.getServletPath()

---

Imported from https://dev.vaadin.com/ issue #19161

[vaadin-bot]

Originally by hesara on 2015-10-20 18:10:05 +0300

---

The path "/vaadinServlet" is an internal one and requests to the root (and certain paths under the root) are automatically forwarded to it. The logging message, while technically accurate (the Vaadin servlet is at those paths and it is another servlet that handles the forwarding to support concurrent use of Vaadin and Spring MVC/REST/...), is perhaps misleading, but otherwise I believe mappings should just work as specified in the application. If nothing is specified, root path is used by default.

If you want to use another path than root, you can either map a UI to another path with @springui("/path/to/my/ui") (which doesn't change the servlet mapping of Vaadin servlet but only the forwarding paths) or map the whole Vaadin servlet to another path with a Spring Boot configuration parameter vaadin.spring.urlMapping (can be set in application.properties, a system property or anything else the Spring configuration mechanism supports) - see https://github.com/vaadin/spring/blob/master/vaadin-spring-boot/src/main/java/com/vaadin/spring/boot/internal/VaadinServletConfigurationProperties.java .

In conclusion, I think only the log messages could be clarified and everything else should work

[pleku]

Old issue for fixing logs but to be honest, we'll probably never get to it due to other priorities - closing the issue.