Posts

resource vs action Command

resource command - can be used for ajax / no need to refresh /    to retrieve images, XML, or any other kind of resource from a Liferay instance. Acction command - get request page refreshing needed

gradle compileOnly dependency

Dependencies required at compile time but never required at runtime (never getting called at runtime)

CIAM / active directory / LDS

Customer Identity Accessibility Management - store user authentication Lightweight Directory Service

SQL Server import/export

import -> restore export -> backup bak file

configuration files under osgi/config

configuration files under osgi/config can be system-wide or portlet level configuration

Hot deploy - Configure workspace

Configure Workspace Create a file in the liferay workspace called  gradle-local.properties  with the following contents. This assumes The workspace is in  c:\liferay\parkland-portal  and liferay was installed in  c:\liferay\liferay-dxp-tomcat-7.1-sp1 # # Set the folder that contains the Liferay bundle downloaded from the # "liferay.workspace.bundle.url" property. The default value is "bundles". # liferay.workspace.home.dir=../liferay-dxp-7.1.10.1-sp1 For theme, try gulp init and target the tomcat server under liferay server

hot deploy vs auto deploy documentation

Hot Deploy Versus Auto Deploy As you develop plugins you’ll want to deploy them to your test servers and as you finish developing plugins you’ll want to deploy them to your production servers. There are  hot  deploy and  auto  deploy options to use in deploying your plugins. Most people confuse the two concepts, believing them to be one and the same. In reality, Liferay has TWO completely separate and different concepts for them. How, you say? We’re glad you asked! This tutorial gives you a brief synopsis of each deployment method. Go ahead and get started by learning about the hot deployment method. USING HOT DEPLOYMENT The first deployment method you’ll explore is  hot  deployment. You may be familiar with hot deployment in the context of Java EE application servers. In summary, you place an application artifact (WAR or EAR) file into a specifically configured directory, your application server (Tomcat, WebSphere, WebLogic, etc.) picks up that artifact, deploys it within the