• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

multi-client web application

 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

JSF based web application has more than one presentation that is one for desktop browsers and one for mobile devices. Searching web and this forum i found two approaches how to accomplish this:
- Use a framework which will handle mobile UI components (MyFaces Trinidad, PrimeFaces)
- Create new or use existing Rendering kit for mobile devices

Because web application will use ajax my current choice is to use for example PrimeFaces for mobile web application. Intention here is to reuse as much as possible.
I understand that since web application uses ajax those component will not be able to render automatically to mobile web application. Plan is to reuse model and controller in JSF and create new view for mobile devices.

Please suggest if this is good approach or any other best practices regarding mobile web application using JSF.


Janez
 
Saloon Keeper
Posts: 27762
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
AJAX only indirectly has to do with rendering. AJAX is mostly about data transfer. However, some mobile devices have only limited JavaScript functionality, so AJAX isn't 100% guaranteed to work.

The ideal approach is definitely to use client-friendly renderkits. The problem, as you've discovered, is that a lot of JSF controlsets only include a desktop HTML renderkit. If you need to support code on mobile devices, ideally you'd have a renderkit that could fall back to non-AJAX solutions when AJAX wasn't availablee.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic