Cookies help us deliver our services.

By using our services, you agree to our use of cookies. Learn more

I understand

Don't expose a Liferay REST service

Who uses Liferay Service Builder knows that it's possible to generate both a local services layer, ie callable by the local JVM, and a remote services layer, that is accessible from a remote JVM typically via web services (REST or SOAP).

The default behaviour is that all methods found in the *ServiceImpl class will be exposed as a web service ones; so let's see how to prevent a single method to be exposed as a service.

Read more: Don't expose a Liferay REST service

Liferay Development Configurator 1.0.0 released

Who works with Liferay knows how much can be tedious and repetitive to prepare a new development environment: download all the needed ZIP files (SDK, Tomcat bundle, portal sources, ...), unzip them, create the workspace, ...

Liferay Development Configurator (LDC) helps to automate this process: just set the project name and the version of Liferay to be used and the program will download and unpack all the files needed.

Read more: Liferay Development Configurator 1.0.0 released

How to use Liferay shared plugin

Liferay allows you to create different types of plugins (portlets, hook, theme, ...) and each of these has its own specific folder inside the SDK.

But there is a kind of plugin, that does not produce a WAR file to deploy, but it is extremely useful because it allows you to create distributable and reusable libraries: it's the shared plugin, and now we'll see how to create and use it.

Read more: How to use Liferay shared plugin