You could simply add a Frequently Asked Question for this.
>> As I said, I don't think GD is needed anymore. Here's an example
>> interceptor I wrote:
>> public class ParameterInterceptor
>> implements ActionInterceptor
>> {
>> // ActionInterceptor implementation ------------------------------
>> public String execute(ActionInvocation invocation)
>> throws Exception
>> {
>> // Set parameters
>> TypeConverter typeConverter =
>> Configuration.getInstance().getAction(invocation.getName()).ge
>> tTypeConverter();
>>
>> OgnlUtil.setProperties(ActionContext.getContext().getParameters(),
>> invocation.getAction(), typeConverter);
>>
>> return invocation.next();
>> }
>> }
>
> 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.
>
>
> -------------------------------------------------------
> 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
--
Michael Blake Day
Artistry Studios
mobile: 770.480.1547
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
