This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

JSF and ADF ... thin versus rich client  RSS feed

 
Derrick Kittler
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One of the appealing aspects of using JSF is that you get an event-driven model typical of rich client apps. I have been looking at JSF for quite a while and the Oracle ADF libs and it appears JSF could be a solid replacement for MVC on Spring or Struts. Having said this, what I would like it the full power of JSF (in my mind) which would give me the ability to target multiple clients with one set of presentation logic and only having to build or otherwise customize the client. What is the reality of this? Is it possible to build and then reuse 80% or more of a standard JSF web app and only have to build or customize the 20% which would be the final UI (rich client or thin client)?
 
Tim Holloway
Bartender
Posts: 18662
71
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is, in fact, one of the primary architectural goals of JSF!
 
Derrick Kittler
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Exactly, this IS the goal but has it happened? Please point to vendors or the open source community where there are examples of JSF-based apps with both say a WIN32 head, a SWT/JFace head and a web browser head. I have an application that I am in the design phase and JSF is one option but I have not found or read solid examples of where it has been deployed to the fullest. Help in this area is greatly appreciated.

Thanks.
 
John Fallows
Author
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is entirely possible to achieve different techology clients using the same JavaServer Faces components, but with different Renderers.

The Oracle ADF Faces component library can render HTML (various desktop browser flavors), Mobile device markup languages (eg. Mobile HTML, WML), Telnet (yes, telnet!), Instant Messenger protocol, etc.

Of course, the screen real estate is quite different in size for some of these different "devices", so that must be taken into consideration while designing applications.

In general, it is practical to use the same component library and skill set to develop your JavaServer Faces application across different technologies and devices. As you can imagine however, it would not be reasonable to expect a complex desktop browser application to be automatically converted to a mobile device.

In our book, Pro JSF and Ajax, Jonas and I show you how to write Ajax-enabled JavaServer Faces components that protect the application developer from the various complexities of each browser technology, while still leveraging the best available browser technologies, such as JavaScript, Microsoft HTC and Mozilla XUL.

Kind Regards.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!