All the hooks we’ve demonstrated so far are scoped to the portal. What if you need to customize specific sites without propagating the customizations throughout the entire portal? You can! Application Adapters are special hooks that let you make changes at the site level. In Liferay 6.1, Application Adapters are used for overriding JSPs.
There’s a Sample Application Adapter in the Liferay Plugins Repository. How do we build an Application Adapter of our own?
To create an Application Adapter, you need a hook with custom JSPs, and you need to turn the hook’s global custom JSP setting off. First, configure your
liferay-hook.xml with the following directives:
When you deploy your hook, Liferay installs the Application Adapter to your instance, under the name of the hook. An Application Adapter hook named Foo becomes available to sites and site templates under the name Foo Hook.
Now, let’s discuss the perks of including the original JSP when overriding it.
Including an original JSP
If you override a JSP from the portal, we recommend you include the original JSP (when possible).
As we already demonstrated, including the original JSP file for global hooks is accomplished by referencing the original JSP file from a
<liferay-util:include> tag and appending the suffix
.portal.jsp to the original file’s name. Here’s what including the original Navigation portlet’s view JSP in a global hook looks like:
<%@ taglib uri="http://liferay.com/tld/util" prefix="liferay-util" %> <liferay-util:include page="/html/portlet/navigation/view.portal.jsp" />
For Application Adapter hooks, we include the original JSP by setting the
useCustomPage attribute to
false, as below:
<%@ taglib uri="http://liferay.com/tld/util" prefix="liferay-util" %> <liferay-util:include page="/html/portlet/navigation/view.jsp" useCustomPage="false" />
The view JSP is specified as
view.portal.jsp as for global hooks.
In the next section, we’ll create and test an application adapter.
Creating an Application Adapter
Let’s create an Application Adapter hook named
example-hook. It will override the Navigation portlet’s
view.jsp, while including the original Navigation portlet’s JSP with some custom text after its contents.
Here’s how we do it:
Modify your hook’s
liferay-hook.xmlto specify the location of your custom JSP and set the global custom JSP setting to
<hook> <custom-jsp-dir>/META-INF/custom_jsps</custom-jsp-dir> <custom-jsp-global>false</custom-jsp-global> </hook>
Create a new
view.jspfile in your hook’s
docroot/META-INF/custom_jsps/html/portlet/navigationdirectory and insert code to include the original JSP:
<%@ taglib uri="http://liferay.com/tld/util" prefix="liferay-util" %> <liferay-util:include page="/html/portlet/navigation/view.jsp" useCustomPage="false" /> <p> This was modified by the Example Application Adapter. </p>
Deploy your Application Adapter hook plugin.
Open your Liferay Portal instance in your web browser and navigate to the site where you’ll use the Application Adapter.
Select Manage → Site Settings. From the Application Adapter field’s drop-down menu, select example. Then click Save.
Navigate back to your site’s Navigation portlet, and make sure that the modification message from your Application Adapter hook plugin’s
view.jspfile is displayed there.
Navigate to a different site’s Navigation portlet to verify that only the content of the portlet’s original
Using Application Adapter hook plugins to override Liferay’s core functionality at the site scope is easy!
You can also apply Application Adapters to Site Templates.
Let’s pretend you want to make an Enterprise Resource Planning (ERP) solution for a company’s departments. Your ERP solution requires an extension of Liferay’s Wiki Portlet, so you implement that extension as an Application Adapter. Then, you incorporate the Application Adapter in a Site Template (named “ERP site”) for the company’s ERP sites. The company’s administrative user creates the sites by going to Control Panel → Sites and adding sites based on the “ERP site” template. The added sites include your Application Adapter automatically.
That’s it for Application Adapters. Let’s learn about performing custom actions through hooks.