Patrick Lightbody wrote:
<snip>
Why not just provide two ServletDispatchers? One that works the way
everything does now (but just reading views.properties) and another that
reads a mapping file that maps path to WebWork alias/action:
mapping.properties:
/secure/Foo.action=Foo
views.properties
Foo.action=Foo
This could be done right now by just writing your own
MappedServletDispatcher, maybe someone should write it and then contribute
it back to OpenSymphony. This is a perfect example where we can add more
features without complicating the basic principle of keeping up-front usage
simple. That's my two cents, but of course, I'll go with whatever the core
WebWork decide.
-Pat
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
