You can check the User-Agent, and acceptable content types, using the same URL, and then apply a stylesheet based on that determination.
-----Original Message----- From: Mike Landis [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 3:10 PM To: [EMAIL PROTECTED] Subject: Re: WAP/WML support to existing application Okey, I could use same actions which would be ok (for wml/jsp pages actions will contain a little bit too much locig). But how about returning the proper jsp page's name (wml or html generation) from action class. First I should check which type of client is requesting the page (wap or browser) or I should use different urls for both html and wml. Which of these two mechanism would be better and where to handle or configure this information? Like I mentioned I would like keep Web based (html) application part as untouchable as possible. Can anyone give hints for that? A small sample application would be great ... does anyone remeber seeing this kind of application? br mike >From: Mark Lowe <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >Subject: Re: WAP/WML support to existing application >Date: Thu, 19 Jun 2003 09:39:46 +0100 > > >The simplist way would be just to have WML copies of your JSP's > >Something like this at the top of you jsp.. (i'll have to check but i think >its correct. JSP's default to contentType="text/html") > ><%@ page language="java" contentType="text/wml" %> > >If you want to minimize repetitive markup between html and wml versions >then some cunning use of tiles and a WML layout could do the job... But >this would really be up to you. Having stuff too rationalized can make >applications harder to maintain.. I'd add new views but use the same >actions. > >The other option would be the parse the HTML version into a WML versions, >personally I think that this is a little more elegant but would confuse >maintainers more. . Youu could go for best of both worlds and do an XSL >transformation at build time to generate the additional jsp's, but unless >your site is huge this could take more time than this would warrant. > >1 issue affecting WML from JSP. >The only problem with WML versions and JSP is that a few of the original >nokia wap phones (7110) have trouble with white space at the top of WML >pages. I worked for an agency where the contact for one of their clients >had one of these phones and it was a pain in the arse. I ended up doing all >my WML as servlets because of the control over white space. You can >replicate this bug with the original version of the nokia wap kit, the >emulator has the same issue. > > >Cheers mark > >On Thursday, Jun 19, 2003, at 06:40 Europe/London, Mike Landis wrote: > >>Hello, >>How or is is possible to add WAP/WML support to existing Struts >>application? >>I would like keep Web based (html) application as untouchable as possible. >>Are there any possibilities to configure Struts so, that WAP and Browser >>requests >>will be handled in their own actions? If yes, how or is it wrong approach? >>In my case there is no need/want to XML/XSLT generation so I can >>'replicate' JSP pages depending on their content type (wml and html). >>Can anyone give me some tips how to add WAP support to existing Web >>application? >> >>Thanks, >>mike >> >>_________________________________________________________________ >>The new MSN 8: advanced junk mail protection and 2 months FREE* >>http://join.msn.com/?page=features/junkmail >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
