>> For one thing, they >> perform better. Another reason is that I have the same situation as Pat, >> the same jsp is the success page for multiple actions. One final reason >> is that the migration path from ww to xw for applications now requires >> filters to handle the (automatic) migration from the old .action urls to >> the new jsp only urls. > > I guess it would be possible to add .action support as well, but if it's > possible to avoid I think we should, for reasons mentioned (hiding > implementation, security).
Maybe this is a little bit of personal preference - but as the webwork (and OS!) way, let's let the user decide! Why can't we just have a ServletDispatcher and a FilterDispatcher? For the record, I actually LIKE having .jspa and .jsp different - it reminds me which pages 'do things' and which are just 'pages'. -mike ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
