Jason Carreira wrote:
I'm not so sure about this case. In this case, you need to map the
interceptor to your classes, rather than it being the default. Yes, we
can work on packages and interceptor defaults, but the fact remains that
if you leave one line out of your xwork.xml, all of a sudden request
params don't get set on your actions which equals lots of confused
emails to the list.
When configuring actions you don't typically specify individual actions, but instead you refer to "stacks" of interceptors. So, most of the time it's going to be a one-liner (i.e. "use defaults"). And if you forget that line, nothing works, so it's not likely to happen (not more than once anyway :-)

/Rickard




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork


Reply via email to