List of instantiable and non-instantiable portlets

A nice to have list of instantiable and non-instantiable portlets:

Non-Instanceable:-
1. Collaboration
  • Blogs
  • Blog Aggregator
  • Calendar
  • Message Boards
  • Recent Bloggers
  • Wiki
2. Community
  • Bookmarks
  • My Communities
  • Page Comment
  • Invitation
  • Page Comments
  • Page Flags
  • Page Ratings
3. Content  Management

  • Document Library
  • Image Gallery
  • Recent Documents
  • Web Content Search
 4. Entertainment
  • Words

5. Finance
  • Currency Converter
  • Loan Calculator

6. News
  • Alerts
  • Announcements

7. Sample
  • Hello Velocity
  • Hello World

8. Shopping
  • Amazon Ranking
  • Shopping

9. Social
  • Activities
  • Requests
  • Top Users

10. Tools
  • Dictionary
  • Language
  • Network Utilities
  • Password Generator
  • Search
  • Sign In
  • Software Catalog
  • Translator
  • Unit Converter

11. Wiki
  • Wiki
Instanceable:-
1. Content Management
  • Asset Publisher
  • BreadCrumb
  • Categories Navigation
  • Document Library Display
  • Navigation
  • Nested Portlets
  • Polls Display
  • SiteMap
  • Tags Cloud
  • Tags Navigation
  • Web Content Display
  • Web Content List
  • XSL Content
2. News
  • RSS

3. Sample
  • IFrame
  • Web Proxy

4. Tools
  • Quick Note

5. Wiki
  • Wiki Display



  • Non-instantiable portlets (eg. Wiki Portlet) can be placed only once in a community or organization of Portal instance.
  • Some non-instantiable portlets (eg. Wiki Portlet) can placed on multiple pages of same community by changing its scope to a specific page. This however is possible Liferay versions > 6 only.
  • Non instantiable portlet can be placed on different page within a community, however they will share the same dataset. eg. wiki portlet in liferay
  • However if still it’s need to have different data set’s of non-instantiable portlets, in can be done by limiting the scope of such portlets to page scope. eg. wiki portlet’s configuration has the option of scope and there it can be limited to current page only, so in can be placed on another page with different data set.



reference: http://michi-path.blogspot.in/2012/03/list-intanceable-and-non-instanceable.html?showComment=1358740911204#c4822921053490272969


Comments

Post a Comment

Popular posts from this blog

jQgrid reload with new data

To reload a jQGrid with fresh data you need to set the data parameter on the grid and invoke reload on it. jQuery("#promotionsGrid").setGridParam({ 'data': newData}).trigger("reloadGrid"); Here newData is a JavaScript array with which I need to re-load the grid. The important thing here is that I had to place this statement just before the grid initialization code even though the reload was expected on change event of a text box. Without that there was simply no effect on my grid!
Read more

Introduction to jQgrid

Introduction Why waste time in developing lists /customizing Liferay OOB search container to display data in tabular format. On top of that more often then not we end up coding for sorting of columns, pagination and formatting some data depending on their values. Trirand has come up with a jQuery plugin called jQgrid. jQgrid supports all of such ease. It provides a nice-looking grid with built-in features such as sorting, editing, search, drill-down, tree lists, and more. It is based upon jQuery and integrates well with Liferay.  The grid is dual-licensed under both the GPL and MIT licenses  (just like
Read more

Rich Client based UI technologies- A Comparison of Thick Client UI tools

Rich Client v/s Thin Client Software developers face many difficult decisions when building new applications, not the least of which is graphical user interface. There are various graphical user interface technologies used, but broadly they can be classified as Rich Client User interfaces and the thin client or web based user interfaces. To understand them better let us look at the history of rich and thin clients. While the Rich client GUI applications would support high quality end-user experience with features such a drag-and-drop, perspectives, customization, high speed local processing; it has had a traditional disadvantage of high deployment and upgrade costs. It was becoming highly difficult and costly to deploy and upgrade these applications. Then came the thin clients or the Web based applications. Thin clients solved many of the deployment and upgrade problems, but that was not without a cost, the cost was in terms of functionality and capability. Thin clients, based on...
Read more