• 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

GWT based portlets in Liferay.

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Instead of using JSF based portlet development, I am thinking to evaluate GWT based approach.
There are many of them. I know Vaadin is already fully supported in Liferay, which is a GWT based toolkit. I haven't seen somebody if tested SmartGWT integration.
Vaadin and SmartGWT both extends GWT but with a different orientation. While SmartGWT is a more client-side implementation, while Vaadin solves most of the problems on the server side.
Which approach fits better on Liferay or in portal environment, I don't know exactly. What is your opinion?
How about the rest of the GWT based implementations in Liferay?
What do you think, is there a serious move toward GWT like approach or JSF will be enough for the coming years?
What about Ext JS approach in Liferay?
 
reply
    Bookmark Topic Watch Topic
  • New Topic