I don't know if this has been mentioned before (maybe multiple times), but don't you all think that it could be very confusing for the developer that defines "success.jsp" as the view for multiple actions and then uses the "access the view as an action" approach?
How would the FilterDispatcher know which action to execute? Also, what if you wanted more than one action to use "success.jsp" as the success page? Michael Blake Day Artistry Studios - e-commerce design, implementation and hosting email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> mobile: 770.480.1547 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Patrick Lightbody Sent: Saturday, March 01, 2003 5:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Prevent access to .jsp > XWork may change this significantly. Nope, this will still work the same way in XWork. However, XWork does add an alternative way to have actions invoked: By using the FilterDispatcher, access to success.jsp will instead intercept that request, execute the action that maps to success.jsp, and then dispatch back to success.jsp. Using the FilterDispatch AND the ServletDispatcher can cause problems sometimes, so it's best if you choose either the "access the view as the action" approach or the "*.action" approach. -Pat ------------------------------------------------------- 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 ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
