Ley de Concierto Económico, LOEPSF y antecedentes normativos. 24

6. If the plugin that you're extending contains a service, you need to overwrite the ClpSerializer.java file. The Service Builder-generated

ClpSerializer.java file contains a hard-coded project for

_servletContextName. You need to change this to the name of your plugin.

This generates a plugin (you can find the WAR file in the /dist folder of your plugins SDK) which combines the original one with your changes.

3.11. Creating Plugins to Share Templates, Structures, and More

Have you ever wanted to share page templates with other users? Are colleagues and clients banging at your door to get a hold of the templates and structures you use for your web content articles and wikis? If so, you can bundle these up in a Liferay plugin to distribute to them. You can even put them in a Marketplace app for them to purchase. When they install your plugin, its templates and structures are automatically imported into their portal's global site. How is this possible? The Templates Importer feature of the Resources Importer app, makes it happen!

Liferay 6.2 Developer Guide Page 137 The Templates Importer is a part of the Resources Importer app. It lets you import the following things:

• Page templates

• Web content templates and structures

• Application Display Templates (ADTs) for any portlet that supports ADTs, such as the Asset Publisher, Blogs, Categories Navigation, Documents and Media, Site Map, Tags Navigation, and Wiki portlets.

• DDL structures and templates, including display templates and form templates.

You can include the template importing capability in any Liferay plugin you develop; but a portlet plugin is the most common type of plugin used for importing templates. Let's build a portlet plugin that imports some templates and structures.

1. Download, install, and activate the Resources Importer app from Liferay Marketplace.

2. Create a portlet plugin project named sample-templates-importer-portlet.

3. Edit your liferay-plugin-package.properties file to include the following property settings:

name=

required-deployment-contexts=\

resources-importer-web

resources-importer-developer-mode-enabled=true

module-incremental-version=1

Here's a summary of what we're accomplishing with these settings: - We remove the plugin's name value to prevent the portal from displaying the plugin as an available app. - Since the Templates Importer feature resides in the Resources Importer web plugin, we include it as a required context. - By enabling developer mode, if the templates we're importing to the Global site already exist on it, the Templates Importer conveniently overwrites them. - Setting the module increment version to 1 is an appropriate version starting point for the plugin.

4. Edit the portlet's portlet.xml file and delete the value of its display-name element to keep the portal from displaying the portlet as an available app.

5. Create a folder named templates-importer in the plugin's WEB-INF\src folder.

This folder will hold all of the templates and structures to import into the portal's Global site.

Let's stop here for a moment and consider how to specify templates and structures. The Templates Importer expects them to be specified in a directory structure under the plugin project's templates-importer folder. You must create folders to contain the template and structure files to apply to the portal.

Here's the directory structure to follow for specifying folders to contain your templates and structures:

• templates-importer/

Liferay 6.2 Developer Guide Page 138

‣ journal/

⁃ structures/ - contains structures (XML) and folders of child structures. Each folder name must match the file name of the corresponding parent structure. For example, to include a child structure of parent structure Parent 1.xml, create a folder named Parent 1/ at the same level as the Parent 1.xml file, for holding a child structures.

⁃ templates/ - groups templates (FTL or VM) into folders by structure. Each folder name must match the file name of the corresponding structure. For example, create folder Structure 1/ to hold a template for structure file Structure 1.xml.

‣ templates/

⁃ application_display/ - contains application display template (ADT) script files written in either the FreeMarker Template Language (.ftl) or Velocity (.vm). The extension of the files, .ftl for FreeMarker or .vm for Velocity must reflect the language that the templates are written in.

• asset_category/ - contains categories navigation templates

• asset_entry/ - contains asset publisher templates

• asset_tag/ - contains tags navigation templates

• blogs_entry/ - contains blogs templates

• document_library/ - contains documents and media templates

• site_map/ - contains site map templates

• wiki_page/ - contains wiki templates

⁃ dynamic_data_list/ - contains dynamic data list templates and structures

• display_template/ - groups templates (FTL or VM) into folders by structure. Each folder name must match the file name of the corresponding structure. For example, create folder Structure 1/ to hold a template for structure file Structure 1.xml.

• form_template/ - groups templates (FTL or VM) into folders by structure. Each folder name must match the file name of the corresponding structure. For example, create folder Structure 1/ to hold a template for structure file Structure 1.xml.

• structure/ - contains structures (XML)

⁃ page/ - contains page templates (JSON)

For templates and structures in your custom plugins, you only need to create folders to support the templates and/or structures you're adding.

Conveniently we've provided a ZIP file of the folders, templates, and structures for the sample-templates-importer-portlet plugin:

1. Download the file sample-templates-importer-contents.zip.

2. Extract its contents into the templates-importer folder of the sample-templates-importer-portlet plugin.

3. Deploy the sample-templates-importer-portlet plugin into a Liferay

Liferay 6.2 Developer Guide Page 139 instance.

The console output should be similar to this:

INFO [localhost-startStop-8][PortletHotDeployListener:343] Registering portlets for sample-templates-importer-portlet

INFO [localhost-startStop-8][PortletHotDeployListener:490] 1 portlet for sample-templates-importer-portlet is available

for use

INFO [liferay/hot_deploy-1][ResourcesImporterHotDeployMessageListener:256]

Importing resources from sample-templates- importer-portlet to group 10194 takes 1294 ms ...

4. View your resources from within Liferay. Log in to portal as an administrator and check the Global site to make sure that your resources were deployed correctly. Here's how you can use the Control Panel to view your templates and structures:

1. Go to Sites in the Control Panel 2. Select the Global site

3. You can view the imported structures and templates here:

⁃ The Journal Article structures and templates can be viewed in the Web Content control panel portlet → Manage → Structures or Manage → Templates

⁃ The Dynamic Data List templates can be viewed in the Dynamic Data Lists control panel portlet → Manage Data Definitions. The templates can be viewed by going to the Actions menu of the Dynamic Data List structure and then clicking on Manage Templates.

⁃ The Application Display templates can be viewed under the Configuration category → Application Display Templates.

⁃ The page templates can be viewed in the Page Templates category from the Control Panel menu

The figure below shows some of the ADTs that were imported.

Liferay 6.2 Developer Guide Page 140 As you take a look around the folders and files within the plugin's templates-importer folder, notice the different kinds of templates and structures.

Page templates are specified in .json files in the

templates-Liferay 6.2 Developer Guide Page 141 importer/templates/page folder. Each one specifies the layout template, web content, assets, and portlet configurations to be imported with that page template.

Here's the contents of the page_3.json file:

{

"layoutTemplate": { "columns": [

"friendlyURL": "/page-3", "name": "Page 3",

"title": "Page 3"

},

"layoutTemplateId": "2_columns_ii"

}

At the bottom of the JSON file, there are several important things specified for the page

template. The layoutTemplateId references the layout template to use for the page. You can specify different layout templates to use for individual pages. You can find layout templates in your Liferay installation's /layouttpl folder. You can specify a name, title, and friendly URL for the page using the respective name, title, and friendlyURL fields. And, although it's not demonstrated in this page template, you can even set a page to be hidden.

Turning your attention to the columns of the JSON file, notice that you can declare portlets by specifying their portlet IDs. To lookup the IDs of Liferay's core portlets see the

WEB-Liferay 6.2 Developer Guide Page 142 INF/portlet-custom.xml file deployed in Liferay on your app server. If you're using the Web Content portlet, you can declare articles to be displayed on a page, by specifying HTML files. Interestingly, the page_3.json file demonstrates using the Nested Portlets portlet to display other portlets: the Search and Currency Converter portlets. Lastly, you can also specify portlet preferences for each portlet using the portletPreferences field.

Tip: You can also import resources, such as web content articles, using the Resources Importer. For example, it's very useful to import web content articles along with a page template that references the articles, in a nested Web Content Display portlet. For more information on importing resources, see Importing Resources with Your Themes.

The figure below, shows a page created using the Page 3 template.

Liferay 6.2 Developer Guide Page 143 Now that you've learned about the directory structure for your templates and the JSON file for the page templates, it's time to learn how to put template and structure files into your plugin. You can create templates and structures from scratch and/or leverage ones you've already created in Liferay. Let's go over how to leverage bringing in XML (structures) and FTL or VM template files from Liferay.

Liferay 6.2 Developer Guide Page 144 The sections below explain how to create structure and template files to put within the defined directory structure of the portlet's templates-importer/ folder.

Structure:

• Dynamic Data Lists: Edit the structure by clicking on Manage Data Definitions. Click on a structure that you want to export and then click on the Source tab. Copy and paste its contents into a new XML file for the structure in the

templates-importer/journal/dynamic_data_list/structure folder. The structure XML sets a wireframe, or blueprint, for a dynamic data list's data.

• Web Content: Edit the structure by clicking on Manage and then Structures. Click on a structure that you want to export and then click on the Source tab. Copy and paste its contents into a new XML file for the structure in the

templates-importer/journal/structures/ folder. The structure XML sets a wireframe, or blueprint, for an article's data.

Template:

• Application Display: Edit the template by clicking on the template you want to export.

Copy and paste its contents into a new FTL or VM file and place it in templates-importer/templates/application_display/[your application display template type]/.

• Dynamic Data List: Edit the template by clicking on Manage Data Definition. Click on Manage Templates from the Actions menu of the structure that your template is linked to.

Choose the template that you want to export. Copy and paste its contents into a new FTL or VM file and place it in

templates-importer/templates/display_template/[structure name]/ or templates-importer/templates/form_template/[structure name]/

• Page: You will have to create the page template from scratch based on the .json file example for the page template above.

Importantly, you must name the files of all structures and templates, except page templates, after their source structures and templates. You can go back to any of the beginning steps in this section to make refinements to the sample plugin to try importing different structures and templates. The final sample-templates-importer-portlet project is available here.

As you've seen for yourself, importing templates and structures with your plugin isn't difficult at all. The Resource Importer app's Templates Importer feature makes it easy. Have fun distributing your templates and structures!

3.12. Summary

You've covered a lot of ground learning Liferay Portlet development. You created a portlet project, studied its anatomy, and created the "My Greeting Portlet". You understood the Action phase and Render phase, and have passed information between them in a portlet. You've enhanced a portlet with multiple actions and have mapped a friendly URL to it. Lastly, you've found how easy it is to start localizing your portlets. You're really on a roll!

Liferay 6.2 Developer Guide Page 145 Now that you know how to create portlets, you'll need to consider a few things, such as

persisting your objects to a database, maintaining separatation between your persistence layer, business logic, and presentation layer, and allowing for flexible implementations. Lastly, you'll want the ability to publish your portlet's operations as services. So how do you address all of this? Hibernate probably comes to mind for persisting your data model, and Spring probably comes to mind with regards to supporting implementation flexibility. Sounds complicated, right?

No need to worry! Liferay's Service Builder helps you build portlet services while hiding the complexities of using Spring and Hibernate under the hood. We'll cover Service Builder next.