Sometimes the best choice depends on your existing skillset or the existing skillset of your development team. Also, the choice might depend on how well supported the technology is within Liferay Portal.
For example, if your team has strong skills with JavaScript, then extending the Liferay MVCPortlet combined with JSP+
AlloyUI would be a good choice. Since AlloyUI is based on YUI, probably best to use YUI utility functions rather than JQuery utility functions. If you are a Liferay EE customer, then Liferay would be able to provide support if you run into problems.
(Note that you can also use JSP+AlloyUI with Struts and SpringMVC portlets).
If your team does not have strong skills with JavaScript, then JSF or Vaadin would be a good choice, because a lot of automatic JavaScript and Ajax features are built into them.
If your team has strong skills with JSF, then
Liferay Faces combined with
ICEfaces,
PrimeFaces, or
RichFaces would be a good choice. Often times development shops choose JSF because it is a Java EE standard, and they want to stay standards-based if they can. Again, if you are a Liferay EE customer, then Liferay support would be able to better support you. If you are also an ICEfaces EE customer, then the
technology partnership between Liferay and ICEsoft would help with resolving any compatibility issues.
If you have strong skills with GWT or
Vaadin, then that's a good choice because there is a
technology partnership between Liferay and Vaadin.
Por favor, faça login para denunciar.
