Announcement Announcement Module
No announcement yet.
Static page strategy Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Static page strategy

    I wanted to get feedback on strategies for managing static pages within a Spring webapp. I am using Acegi to manage security and want to provide a public and private zones.

    I like having the Spring DispatcherServlet mapped to *.htm. I mapped Acegi to restrict access to URI secure/*. This leaves me with a few options for static pages.

    1. Use the extension *.html for static pages. However, I don't like this because it is, so similar to the DispatcherServlet mapping. On the other hand it seems to be the least restrictive option.

    2. Use forwards to access static pages through Spring. This seems like a lot of unnecessary overhead and a maintenance nightmare.

    3. Map the DispatcherServlet to a path such as /spring/*.htm. Then static pages can be anywhere, but the /spring directory and use same extension *.htm.