Introduction #

The Asset framework allows any type of content to be displayed/edited/added in asset publisher. These type of content that use this framework are called assets and can be classified using tags and categories.

Assets defined in Core portlets #

By default, in the portal there are several types of content (assets) that implement the Asset Framework:

  • Web Content
  • Image Gallery Image
  • Blog Entry
  • Document Library Document
  • Bookmark
  • Message Board message
  • Wiki page
  • Calendar Event

And in the plugins, we have:

  • Knowledge Base article

Disabling predefined assets #

Assets from the portal can be disabled using this property from portal.properties:

    #
    # Set a property with the prefix "asset.renderer.enabled." and a suffix
    # with the asset renderer factory class name to enable or disable an asset
    # renderer factory. The default setting is true. See LPS-6085 for more
    # information.
    #
    #asset.renderer.enabled.com.liferay.portlet.documentlibrary.asset.DLFileEntryAssetRendererFactory=false

Using the asset framework in custom portlets #

You can also create your own assets in a plugin using this framework. For detailed instructions check the chapter about the asset framework in the Developer Guide (direct links per version provided below):

Moyenne (2 Voter)
L'estimation moyenne est de 1.5 étoiles sur 5.
Commentaires
Réponses Auteur Données
A very nice feature indeed. Also the... Michael Lustenberger 5 avril 2013 03:03

A very nice feature indeed. Also the documentation (for 6.1 by now) is straight forward. The only missing point was how to let the Asset Publisher know about my custom portlet, but adding the <asset-renderer-factory>foobar</asset-renderer-factory> tag to the liferay-portlet.xml solved the problem (see liferay-portlet-app_6_1_0.dtd for details). Thanks guys!
Publié le 05/04/13 03:03.