Book Image

Liferay Portal Systems Development

Book Image

Liferay Portal Systems Development

Overview of this book

Liferay portal is one of the most mature portal frameworks in the market, offering many key business benefits that involve personalization, customization, content management systems, web content management, collaboration, social networking and workflow. If you are a Java developer who wants to build custom web sites and WAP sites using Liferay portal, this book is all you need. Liferay Portal Systems Development shows Java developers how to use Liferay kernel 6.1 and above as a framework to develop custom web and WAP systems which will help you to maximize your productivity gains. Get ready for a rich, friendly, intuitive, and collaborative end-user experience! The clear, practical examples in the sample application that runs throughout this book will enable professional Java developers to build custom web sites, portals, and mobile applications using Liferay portal as a framework. You will learn how to make all of your organization's data and web content easily accessible by customizing Liferay into a single point of access. The book will also show you how to improve your inter-company communication by enhancing your web and WAP sites to easily share content with colleagues.
Table of Contents (17 chapters)
Liferay Portal Systems Development
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface

Webs plugins


Webs plugins are regular Java EE web modules designed to work with portals, such as ESB (Enterprise Service Bus), SSO (Single Sign-On), workflow engine, search engine, and so on. A web plugin provides the ability to integrate third-party applications, supporting embedding hook definition and service-builder services, which is different from plain web applications.

Web plugin project

Similar to the project name of a portlet or hook, a web plugin project should have the name ${web.name}-web, under the folder $PLUGIN_SDK_HOME/webs. For example, the name ${web.name}-web could be cas-web or solr-web . Since there isn't any template for web projects, you have to create a web project manually.

The web project is made up of build.xml, an application WAR file (if using web application WAR directly), and a folder called docroot. For example, the web plugin cas-web has the following definitions in the file build.xml:

<?xml version="1.0"?>
<!DOCTYPE project>
<project name...