- Liferay experiences thread link
- Public render parameter(JSR 286) in liferay to read a request parameter: link
- Website search (page search based on meta tags : link
- Building a hello word portlet using plugins SDK:link
- Liferay and opensso integration:(quite neat) : link
- Organization vs community : link
- Adding validation messages in liferay : link
- Popup in liferay : link
- Liferay hook plugins : link : Hooks are event handlers and they are Good stuff !. Liferay provides the following events : Application Startup Events, Login Events, Service Events Gotchas : Better to use hooks as plugins. Tried in ext once and it broke other hooks.
- Customizing labels(internationalized): Done in Language-ext.properties
: link - A good review of liferay 5.x is here
- Liferay architecture is SOA based :
* Above image is taken from book Liferay Portal 5.2 Systems Development.pdf
1 comment:
Liferay organization vs communities:
We have two levels of resource organization in liferay
1. Organization
2. Community (which liferay uses by default out of the box)
Organization models the real world organization structure
lets say Uniliver is the top level organization
Dove, Flora, Lipton etc can be sub organizations
clearly there is a hierarchy in the organization
Now for 2., community is a cross cutting thing say health and fitness website for uniliver which the entire organization would use
So it would make sense to use 1.Organization group for maintaining templates
However I am not sure whether organization has staging and workflow support
like Community
I think its more of an architectural decision whether to keep velocity templates in 1. or 2.
Ref: Liferay administration guide 5.2.pdf page 87 onwards
Post a Comment