Menu
I'm building a single page application which does all of it's html request routing on the client side and on the backend it uses dropwizard to provide a bunch of JSON services.
Essentially I'm having trouble getting the jetty in dropwizard to serve index.html for every request except to the following paths:
/css
/i18n
/img
/js
/lib
/services
/templates
In fact I'm having a lot of trouble finding documentation that tells you how to setup any http routing at all. (I'm not a java guy).
Here's my simple yaml config:`
http:
port: 8082
adminPort: 8083
rootPath: /service/*`
What do I need to add to acheive this.
Thanks
838
Dropwizard is an open-source Java framework used for the fast development of high-performance RESTful web services. It gathers some popular libraries to create the light-weight package. The main libraries that it uses are Jetty, Jersey, Jackson, JUnit, and Guava. Furthermore, it uses its own library called Metrics.
Dropwizard uses Logback for its logging backend. It provides an slf4j implementation, and even routes all java. util. logging , Log4j, and Apache Commons Logging usage through Logback.
Jetty for HTTP Because you can't be a web application without HTTP, Dropwizard uses the Jetty HTTP library to embed an incredibly tuned HTTP server directly into your project.
A Dropwizard Bundle is a reusable group of functionality (sometimes provided by the Dropwizard project itself), used to define blocks of an application's behavior.
I've done this without changing my configuration. In fact, it only took me one line of code, to be put in the initialize method of my Application class:
bootstrap.addBundle(new AssetsBundle("/app", "/", "index.html", "static"));
Which basically says to serve anything under /app inside my JAR file under the URL pattern /, with index.html as the default file. This bundle will be named static, but you could pick whatever name you like.
Note that I'm using version 0.7.0-rc2 of Dropwizard, I'm not sure whether it works for earlier versions as well.
173
@mthmulders answer worked for me when I went to "/" and would work on other url's while the page had not reloaded, but would not work when I refreshed the page at "/foo/bar/bash" or any other url. I fixed this issue by mapping any 404 response to return back the index.html page instead.
Add your static assets to your initialization method of your Application class:
bootstrap.addBundle(new AssetsBundle("/app", "/", "index.html", "static"));
Add the mapping to your new 404 page to your run method of your Application class:
ErrorPageErrorHandler eph = new ErrorPageErrorHandler();
eph.addErrorPage(404, "/error/404");
environment.getApplicationContext().setErrorHandler(eph);
Add your resource that maps to /error/404
@GET
@Path("/error/404")
@Produces(MediaType.TEXT_HTML)
public Response error404() {
// get html file from resources here...
return Response.status(Response.Status.OK)
.entity("<html>foo</html>")
.build();
}
After doing this I was able to refresh the page at "/foo/bar/bash" and it still returned back the index.html file.
29
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
