CODEWITHSUNDEEP
springspring-bootthymeleaf
Bob Brown
Bob Brown

Reputation: 1098

Spring Boot gives "TemplateInputException: Error resolving template" when running from jar

I have an app that works perfectly when started within IntelliJ or via gradle bootRun.

however, if I do gradle bootRepackage and then try and run the resulting jar, I end up with:

2014-12-02 21:46:14.086 ERROR 9839 --- [nio-2014-exec-2] org.thymeleaf.TemplateEngine             : [THYMELEAF][http-nio-2014-exec-2] Exception processing template "/login": Error resolving template "/login", template might not exist or might not be accessible by any of the configured Template Resolvers
2014-12-02 21:46:14.087 ERROR 9839 --- [nio-2014-exec-2] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/login", template might not exist or might not be accessible by any of the configured Template Resolvers] with root cause

org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/login", template might not exist or might not be accessible by any of the configured Template Resolvers
    at org.thymeleaf.TemplateRepository.getTemplate(TemplateRepository.java:245)
    at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1104)
    at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1060)
    at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1011)
    at org.thymeleaf.spring4.view.ThymeleafView.renderFragment(ThymeleafView.java:335)

I can see that the jar has /templates/** contained in it. the content looks OK to me.

One possible(?) factor may be that I use an html page referring to a layout, thus:

  layout:decorator="layouts/main"

I can confirm that the file IS in the jar.

/login is defined thusly:

@Override
public void addViewControllers(ViewControllerRegistry registry) {
    registry.addViewController("/login").setViewName("/login");
    registry.addViewController("/").setViewName("/login");
}

and I have spring security configured as:

@Configuration
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {

@Override
public void configure(WebSecurity security) {
    security.ignoring().antMatchers("/assets/**");
}

@Override
protected void configure(HttpSecurity http) throws Exception {
    http
            .csrf().disable();
    http
            .authorizeRequests()
            .antMatchers("/").permitAll()
            .anyRequest().authenticated();
    http
            .formLogin()
            .loginPage("/login")
            .defaultSuccessUrl("/home")
            .failureUrl("/login?error")
            .permitAll()
            .and()
            .logout()
            .invalidateHttpSession(true)
            .logoutSuccessUrl("/login?logout")
            .permitAll();
}
}

I think that's all that might be relevant to this issue...

I have seen https://github.com/spring-projects/spring-boot/issues/112 and Proper location of Thymeleaf views for Spring (amongst others). These resources notwithstanding, I have not been successful at getting template resolution working.

Any suggestions gratefully recieved.

To have come so far with Spring Boot yet to have stumbled at the last hurdle (near-final deployment) is vexatious.

Upvotes: 23

Views: 92626

Answers (10)

Thomas Adrian
Thomas Adrian

Reputation: 3636

My problem was that I had named the templates directory with a capital T. "Templates"

renaming to "templates" resolved it

Upvotes: 0

shashigura
shashigura

Reputation: 153

This issue is with @Restcontroller because @RestController annotation is mix of @responseBody and @controller annotation

RestController default response body is json or string format what ever string html name is added its consider as string then its display string in the default html

change @restController to @ controller then it will work

Upvotes: 2

CanCoder
CanCoder

Reputation: 1150

For me there was nothing wrong with my code. All I did was run the mvn clean command in my terminal then restart the app again and it worked fine.

Upvotes: 1

Henry Patrick Karugendo
Henry Patrick Karugendo

Reputation: 11

If the above solutions don't work for you, like me,

I changed my Controller to a RestController. It fixed my issue.

This is, if you are using a Front End App like Angular to talk to your Back-end application.

Upvotes: 1

firstpostcommenter
firstpostcommenter

Reputation: 2931

I faced the issue when using the spring-boot-starter-thymeleaf dependency

So I have used the below dependency instead,

        <dependency>
            <groupId>org.thymeleaf</groupId>
            <artifactId>thymeleaf</artifactId>
            <version>3.0.9.RELEASE</version>
        </dependency>

Upvotes: 2

Paulo Cesar Pengo
Paulo Cesar Pengo

Reputation: 1

After many of tentatives I found a way to resolve my problem about the template error. I dont know if is related to the new version of spring-boot but my change worked.

Every request throught controller instead of returning String "/login", for example, I change to create a object ModelAndView: 

@RequestMapping(value="/login", method=RequestMethod.GET)
public ModelAndView login() {
    ModelAndView mv = new ModelAndView("login");
    return mv;
}

hugs to all.

Upvotes: 0

s332401890
s332401890

Reputation: 121

spring.thymeleaf.prefix=classpath:/templates/

change

@Override
public void addViewControllers(ViewControllerRegistry registry) {
    registry.addViewController("/login").setViewName("/login");
    registry.addViewController("/").setViewName("/login");
}

to

@Override
public void addViewControllers(ViewControllerRegistry registry) {
    registry.addViewController("/login").setViewName("login");
    registry.addViewController("/").setViewName("login");
}

the view name should be Relative path

Upvotes: 0

user2822874
user2822874

Reputation: 169

I had same problem using spring boot with thymeleaf by default configuration. All worked until I have to try .jar

message says: ... org.thymeleaf.exceptions.TemplateInputException: Error resolving template "/fragments/footer"

I solved playing with / , problem was that they don't need the slash.

I Changed this:

<footer class="footers" th:replace="/fragments/footer :: footer">

for this:

<footer class="footers" th:replace="fragments/footer :: footer">

Upvotes: 16

Michael Hegner
Michael Hegner

Reputation: 5843

Okay, I found where you have to take a close look. In your Controller classes, when you use @RequestMapping on class, no leading slash (e.g. @RequestMapping("property")). On Method you need a leading slash (e.g. @GetMapping("/list")) and the return value no leading slash (e.g. return "property/list";)

An Example Snippet

@Controller
@RequestMapping("property")
public class PropertyController {
    @NonNull PropertyService service;

    @GetMapping("/list")
    public String list() {
        return "property/list";
    }
}

Upvotes: 6

Bob Brown
Bob Brown

Reputation: 1098

The answer seems to be here: https://github.com/spring-projects/spring-boot/issues/1744

In a nutshell: if a resouce path contains '//', things go awry.

The fix is to modify application.yml thusly:

spring:
  thymeleaf:
    prefix: classpath:/templates

(the fix is similar for a .properties file, of course)

The knock-on effect is that all references to templates or whatever need to be preceeded by a slash, as in (Thymeleaf .html file):

      layout:decorator="/layouts/main"

or (Groovy controller):

@RequestMapping(value = "/home", method = RequestMethod.GET)
def home(Model model, Principal principal) {

    "/home/home"
}

I think that spring boot should fix this. Urgently. This is REALLY bad ergonomics that blows up badly, just at the point where one feels like one is nearing final deployment.

Upvotes: 11

Related Questions