>Now, ob. webwork: there are two ways you could approach the user-agent
>thing: one is to have an action choose a view based on useragent headers
>(available through ServletActionContext, IIRC). This action would be
>chosen last in the action chain.

A cleaner approach would be to extend ConfigurationViewMapping, and alter
the result of the parent getView() call based on the user agent. The user
agent is retrievable via ActionContext.getRequest(). This way, the mapping
occurs without any extra effort in action.xml etc etc.






-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to