Selon Jason Carreira <[EMAIL PROTECTED]>: > Sorry, I don't mean to be rude either... I'm just saying that making a class > extensible is highly dependent upon which points you need to be able to > extend / override so it's best you work it out and let us know what you'd > like to change. > > At its heart, ServletDispatcher is very simple... It takes the incoming URL > and maps it to a namespace and an Action name then creates an ActionProxy and > executes it... All you need to do is figure out how you want to do this > mapping.
Yep. This means that the mapping strategy should be defined out of the servlet. That way if the ServletDispatcher provides extensibility (somehow like the possible refactoring I wrote earlier), we could write a RewritePathServletDispatcher that could apply the trick outlined in Turbine. Are some of you in need of such a thing? If so, I would be glad to have some feedback on your expectations... Regards, Jérôme. ------------------------------------------------------- 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
