The exception route we created work doesnt work for the / or for /ideas. Why?

Those routes never call the "findBySlug" method on CourseIdea that throws the exception we're handling. I believe if you wanted to catch those errors, then you might be able to create a catch-all route at the bottom of all the routes, just above the exception handlers in main, that matches any route the others haven't, and return a new custom exception. This pattern is standard boilerplate in an express app, and I'm pretty sure the same convention would apply here.

Hi Timothy, the exception route created for the course was made for NotFoundException class, which was only implemented within the CourseIdea model -> this model was only used for pages rendered under /ideas/ directory, so you will only see the custom error page we created for any pages you attempt under "http://localhost:4567/ideas/". You will get the standard 404 page by Jetty for all the other non-existing pages beyond /ideas/.

For example, you will see the not-found.hbs template for http://localhost:4567/ideas/fswou837 but NOT for http://localhost:4567/ideasfswou837.

Also, double-check and make sure you did not miss a single line from the exception block we did from the course video:

exception(NotFoundException.class, (exc, req, res) -> {
            res.status(404);
            HandlebarsTemplateEngine engine = new HandlebarsTemplateEngine();
            String html = engine.render(new ModelAndView(null,"not-found.hbs"));
            res.body(html);
        });

Hope it helped :)

Hello everyone!

i just stuck a bit as well on this as Timothy Boland described. I have read Nicolas Hampton 's answer and i manage to do something like this.

get("/*", new Route() {
            @Override
            public Object handle(Request request, Response response) throws Exception {
                    HandlebarsTemplateEngine engine = new HandlebarsTemplateEngine();
                    String html = engine.render(new ModelAndView(null, "404.hbs"));
                    throw new NotFoundException(html);
            }
        });

and in the NotFoundException class i created a new constructor that takes as parameter a string. Like this... So it renders the 404 page.

public class NotFoundException extends RuntimeException {

    public NotFoundException() {
    }

    public NotFoundException(String message) {
        super(message);
    }
}

Tell me if this is a proper way to handle those requests Craig Dennis.

Thanks a lot guys! :)