Guidelines for choosing portlet framework and JSF component Suite

[9年前 に Mahesh Nanavate によって更新されました。]

Hi All,

I am new to Liferay. I am using Liferay 6.2 on Tomcat 7. When creating a Liferay Portlet Plugin project, I see the following options:

Under Portlet Framework:

1. Liferay MVC
2. JSF 2.x
3. Vaadin


Under JSF Component Suite
1. JSF Standard
2. ICEFaces
3. Liferay Faces Alloy
4. PrimeFaces
5. RichFaces

Are there any guidelines as to when should one go with what portlet framework and what JSF component suite ?

Also, will RichFaces only work with Liferay on JBoss?

Thank you!

Best Regards,
Mahesh

[9年前 に Neil Griffin によって更新されました。]

Hi Mahesh,

Welcome to the Liferay community!

Mahesh Nanavate:

Are there any guidelines as to when should one go with what portlet framework ... ?

Liferay Portal is designed to be agnostic about portlet frameworks. So the choice is yours. David Nebinger (a stalwart member of our community) typically recommends "go with what you know", meaning whatever skills your developers currently have, then utilize those skills. If they are HTML/CSS/JS type developers, then the Liferay MVCPortlet might be best. If they are server-side Java type developers, then perhaps JSF or Vaadin would be a better option.

Mahesh Nanavate:

Are there any guidelines as to when should one go with what ... what JSF component suite?

If you choose JSF, then you have the choice of using PrimeFaces, ICEfaces, RichFaces, or Liferay Faces Alloy. We are currently developing a new version of Liferay Faces Alloy that is designed to make it possible for your JSF portlets to look and behave like Liferay out-of-the-box portlets. For more information, refer to the Liferay Faces Showcase and the 4.2.0-m2 release announcement.

Mahesh Nanavate:

Also, will RichFaces only work with Liferay on JBoss?

The Liferay Faces team has worked hard to make RichFaces compatible with Liferay Portal via Liferay Faces Bridge. JBoss is making good progress towards a path of stability with RichFaces 4.5, but we probably won't see innovation or new components in RichFaces in the future.

Kind Regards,

Neil

[9年前 に David H Nebinger によって更新されました。]

Neil Griffin:

David Nebinger (a stalwart member of our community) typically recommends "go with what you know", meaning whatever skills your developers currently have, then utilize those skills.

Thanks Neil!

A big reason to stick with what you know is that it can help lessen the Liferay/portlet learning curve. When you're new to Liferay, there's a lot of stuff to learn and get familiarized with (although the Liferay training and Liferay in Action are great helps). But the last thing you want to do is, at the same time, trying to learn a new framework on top of it. When things go wrong you're left wondering if it is an issue with your Liferay understanding or an issue with your framework understanding, ...

[9年前 に Vernon Singleton によって更新されました。]

It is refreshing to see a forum where there are no flames.
A place where people are informed and comforted instead of being ignored.

Thank you for your question, and the courteous, professional answers.