1. Inici
  2. Development
  3. Setting up a portlet development environment

Setting up a portlet development environment

686783, modificat fa 18 anys.
Setting up a portlet development environment
New Member Apunts: 2 Data d'incorporació: 15/04/08 Publicacions recents
I have been searching the internet trying to find information on developing portlets to 'install' into LifeRay. Everything that I find points me back to the "Liferay Portal 4 - Development in the Extension Environment guide".

Is is true that I need to install a Liferay development environment with the Liferay source code in order to add portlets to Liferay? I am really starting to get confused.

Thanks...
thumbnail
464774, modificat fa 18 anys.
RE: Setting up a portlet development environment
New Member Apunts: 20 Data d'incorporació: 08/02/08 Publicacions recents
Haha User:
I have been searching the internet trying to find information on developing portlets to 'install' into LifeRay. Everything that I find points me back to the "Liferay Portal 4 - Development in the Extension Environment guide".

Is is true that I need to install a Liferay development environment with the Liferay source code in order to add portlets to Liferay? I am really starting to get confused.

Thanks...


No. You don't have to. You can develop JSR-168 standard portlets to deploy in Liferay. You would just have to add a few liferay specific XML files to identify them. Here's a resource that may help you.

http://spaquet.blogspot.com/2008/02/building-portlets-for-liferay-44-with.html
thumbnail
682861, modificat fa 18 anys.
RE: Setting up a portlet development environment
Liferay Legend Apunts: 1228 Data d'incorporació: 14/04/08 Publicacions recents
Haha User:
Is is true that I need to install a Liferay development environment with the Liferay source code in order to add portlets to Liferay? I am really starting to get confused.


dog bert:
No. You don't have to. You can develop JSR-168 standard portlets to deploy in Liferay. You would just have to add a few liferay specific XML files to identify them. Here's a resource that may help you.


We also found that using extended environment is asking too much; using JSR-168 is too restrictive (can not use core Liferay functions).
So for a couple of years we successfully use a mixed approach - liferay-specific hot-deployed portlets. This environment has not suffered at all during liferay upgrades.
WAR files are very light, as they do not carry liferay jars, only project-specifc config files, jsps and action classes.