13. Permissions API
The good
• Versatile system
• Commonly required API’s are from out of the box
• Permissions & Authentication API
• UI to handle changes to the users
• Tag library for JSP pages
• Easily modified and extendable for custom portlets
12.9.2013 www.ambientia.net 16
The bad
• It is a complicated system and has learning curve
14. Liferay’s permission data model
12.9.2013 www.ambientia.net 17
See, it is
quite
complex...
One day to
learn – one
year to
master
16. CMS Functionality
The good
• Flexible content structure and display definition i.e.,
Structures and Templates
• Versatile document storage (i.e. excellent API’s)
• Content versioning
• Scheduled publishing of content
• Workflow capabilities
• Articles can be integrated easily to custom portlets
12.9.2013 www.ambientia.net 19
The bad
• The UI a bit challenging
20. Asset Framework
The good
• Shared storage and display for various content items in the
application
• Custom portlets can be integrated to the Asset Framework
and can be published as assets
• Categories; tags; commenting; etc.
• Display styles and methods can be set based on the content
type
12.9.2013 www.ambientia.net 27
The bad
• Again, correct Asset Framework usage requires learning
• The Asset Publisher and other display portlets require
modification almost each time they are being used
because the OOTB setup seldom meets the project’s
requirements
24. Sites and Organisations
The good
• Staging functionality
• Private and public pages
• Can have unique domain names
• Content can be structured to sites with different rights
• Page and Site Templates enables fast structure
management and modification
12.9.2013 www.ambientia.net 31
The bad
• Site versus organisation selection can be tricky
• Data migrated via large lar pakages
27. Service Builder
The good
• Easy data structure mapping and finder mapping with XML
• Can be finetuned with portlet-model-hints.xml
• Automatic service layer generation
• Easy extension of the default interfaces
• Permissions Framework works nicely with the Service Builder
• Multiple portlet apps can use dependencies from each other
12.9.2013 www.ambientia.net 34
The bad
• Automatically generated code is difficult to accept for certain
developers
• It is difficult to fix bugs in the generated code
31. Techologies and componets not used
1. Liferay’s CE- version
2. Most of the OOTB portlets
• Liferay has a large set of portlets included but
only a few of them are commonly used when
building custom applications
3. Struts Framework
• Commonly replaced by Spring or Liferay MVC
• On some cases needs to be used
4. Ext environment
• Is replaced by hooks in most cases
12.9.2013 www.ambientia.net 39
35. Newolo
• It did not require a Portal as such it benefits a lot of about
• Permissions API: user Authentication and Authorisation
• Service Builder
• UI with JSP & JSTL
• SOAP based integration with custom made content
repository
• Application architecture utilizes site structures to enhance
logic and manageability
• Themes and layouts for multiple clients
• Documents and Media to update videos to the system
• Localization for all content
• Liferay scheduling to send reminders
• Therefore, Liferay is being used in a custom application
12.9.2013 www.ambientia.net 43
37. Liferay is
good for
custom
applications
1) OOTB
Developer
Functionality
2) OOTB
Portal’s
management
interfaces
3) Portal’s
footprint is
not an issue
with modern
hardware
4) Decent
licensing
model for
single app
usage
12.9.2013 www.ambientia.net 46