In principle, you just need a servlet that will serve the files, or configure your web app to do that.
<ot> In practice, it's usually a *lot* cleaner to use a web server like NginX to reverse proxy your web api and serve your static files - that way your web app is only concerned with what it's good at (implementing a REST api), and static files are served by a web server which is better at that sort of thing. That also makes it trivial to embed Jetty or similar, get rid of all of your XML config files and have a server you can run with java -jar - which, at least to my taste, eliminates a huge source of problems and development slowdowns which, in this day and age, adds zero value (any technology which generates questions like "How do I do this thing in my complicated XML configuration file" *ought* to be generating the question "Why am I using something that has XML configuration files?"). </ot> -Tim -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
