best practices for creating output for different clients

[Martin Kindler <ki...@arcor.de>]

Hi all,

I'ld like to to know whether there are best practices established in the
Struts community to create (different) output for different clients (e.g
PC-based browsers, mobile phones, PDAs, speech, etc.)
I thought of various possibilities: using Cocoon for the presentation
layer (an additional tool to learn :-(), defining different actions for
different clients (maintenance!)  or manipulating the action mapping i.
e. extend a declaratively specified action myAction to client specific
actions myIEAction, myPalmAction, myNokiaAction, ... with e.g. a
different path for each one (where to add the hook? possible problems
when upgrading to newer versions of Struts).

What is the common approach to this problem?

Martin Kindler



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org