Versions Compared

Old Version 5

changes.mady.by.user Unknown User (cameronbraid)

Saved on

compared with

New Version 6

changes.mady.by.user Unknown User (cameronbraid)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • We need to provide a developer friendly way of exposing webwork static resources - primarily javascript files
    1. User could copy them into a folder
      • This either requires a separate zip download or packaging these files within the jar
      • This is a bad idea because it is error prone when the user upgrades
    2. Provide a resource loading servlet that serves the resources from the webwork jar
      requires a servlet definition and mapping in web.xml
      • could use a webwork.properties setting for the servlet prefix to allow user to 'mount' the static resources under a different prefix
        this makes jar upgrades easy and transparent
      • I have a prototype of this working in one of my apps - however it is restricted to mounting a single package on a single prefix. No support for multiple mappings.
        No Format
        i.e.  mount com.opensymphony.webwork.static at /webwork 
request /webwork/validationAjax.js 
loads  com.opensymphony.webwork.static.validationAjax.js
    3. Get the validationServlet to serve the javascript code. Use '/validationServlet/client.js' as the url
    4. Any other ideas ?

...