Re: Struts and WML

[Taylor Cowan <ta...@bondisoftware.com>]

I think your last paragraph touches on the best solution.  Tags are not
HTML, they are XML.  Tags could produce their underlying content as XML,
then detect the client based on something in the request, and appy an XSLT
for a particular client type.  This would require some additional tag
infrastructure to abstract the XSLT access and cataloging, something like a
base class called ClientNeutralBodyTag that helped tag designers get to the
XSLT storage.  Actually tags are one way to simplify client neutral JSPs.

Some tags are certainly generic enough to have alternate representations as
HTML and WML.

Taylor


----- Original Message -----
From: "Shun, Vadim" <VS...@newcorp.com>
To: "'Struts'" <st...@jakarta.apache.org>
Sent: Friday, August 25, 2000 10:29 AM
Subject: Struts and WML


> Hi,
>
> is there any way to make struts (or generic JSP model 2 application)
> compatible with WML, in addition to HTML.
>
> As I see,struts is heavily geared (as JSP in general) towards HTML
> generation with tag libraries, etc. This makes it very practical and
useful
> for HTML applications.
> However the ideal approach would be to allow WML generation for wireless
> clients.
>
> Would the solution of JSPs generating XML instead of HTML, discussed a few
> months ago on JSP-interest mailing list as JSP model 2.5, work? By
applying
> 2 different stylesheets to resulting XML data we would achieve HTML, as
well
> as WML (or whatever else format is popular in future for client device).
> Alternatively, controller could determine client type (Mozilla? wireless)
> and, based on the type, forward control to appropriate JSP maintained
> specifically for that client (that approach would require having 2 sets of
> JSPs - one for HTML and another for WML client).
> I am somewhat unclear on how practical these approaches are. Are they
> feasible at all?
>
> Yours,
>
> Vadim Shun
> NEW Corp
> Dulles, VA