3 He has worked on the following books: Liferay Portal Enterprise Intranets, , ISBN ; Liferay Portal Systems Development, , ISBN ; Liferay. The world's leading open source portal. Download Latest Version liferay-ce- ronaldweinland.info ( MB) Get Updates. Liferay Portal Systems Development Book CoverLiferay Portal Here you can find informations about some social portlets that you can download from SVN and Sample Chapter 5 - Managing Pages [ MB] (PDF).
|Language:||English, Spanish, Hindi|
|Genre:||Science & Research|
|ePub File Size:||18.81 MB|
|PDF File Size:||12.82 MB|
|Distribution:||Free* [*Register to download]|
Liferay Portal Systems DevelopmentBuild Java-based custom intranet systems on top of Liferay portalJonas X. Yua. Liferay Portal Systems Development. Jonas X. Yuan. pages. 16 hours 33 minutes. Liferay Portal Systems Development. document titled Liferay Portal Systems Development is about Internet and Web Development. Download at ronaldweinland.info Credits A.
Download the Liferay Portal 5. Unpack the Liferay distribution and fire it up. Make sure you can log in as the test liferay. Create a test user. Remember the email address. Make sure you create a home directory. Verify that you can log in as your test user.
What this book covers In Chapter 1, we look at what Liferay portal is and why we should use it. Then we introduce the Liferay portal architecture and framework. Liferay portal can be extendible at three levels—Plugins SDK environment, Extension environment, and Liferay portal source code. Finally, we discuss portal development strategies in detail. In Chapter 2, we cover the experience of Liferay portal and portlets, using JSR portlets, employing portlet configuration, context, request, response, and preferences, extending JSR portlets, serving resources, and coordinating portlets.
It helps you to build larger applications and re-use portlets in different scenarios. This material is copyright and is licensed for the sole use by Richard Ostheimer on 20th June hilda ave. In Chapter 4, we include experiencing Struts portlets in our discussion, where we first discuss how to develop a JSP portlet.
Then we introduce how to develop a basic Struts portlet in Ext—defining the portlet, and specifying page action, and page layout. Accordingly, we also introduce how to develop an advanced Struts portlet in Ext—redirecting, adding more actions, setting up permissions, and so on.
Finally, we address how to use Struts efficiently. In Chapter 5, we first look at extending the Communities portlet, then we move on how to customize the Manage Pages portlet.
We also look at how to customize page management with more features, and use communities and layout pages in an efficient way. Then we introduce how to customize FCKeditor to make images, links, videos, games, video queues, video lists, and playlists a part of web content.
In Chapter 8, we look at how to build My Community in general, and how to customize and extend this feature as well. First, we introduce how to share web site, pages, or portlets with friends. Then we introduce how to customize My Account and how to build My Street with personalized preferences.
It introduces how to build layout templates in Ext first. Then it discusses how to build layout templates and themes in Plugins SDK and how to add Velocity services in themes. Finally, it addresses how to use Plugins SDK in an efficient way.
We introduce Control Panel first—how it works and how to customize it. Later, we discuss how to set up Social Office themes and portlets, and how to hook language properties, and portal properties. Finally, we discuss an efficient way to use hooking features.
Under the folder there is a folder named docroot and an XML file named build. As you can see, build. When using Ant target create, it will create a new portlet project.
Under the folder docroot, it includes a css folder with a CSS file main. Inside these XML files, you will find that the template variables, and are in use. As mentioned earlier, Ant target create will create a new portlet project based on three parameters: portlet. Note that the parameters portlet. What's happening when you use Ant target create? This Ant target does roughly the following tasks: Checks portlet. In detail, the generated portlet project includes a folder docroot and the build.
Under the folder docroot, it includes a css folder with the CSS file main. This section will use the knowledge base project, as mentioned in the previous section. Under the folder, you will see the docroot folder and the build. For fast development, you can add the XML file knowledge-base-portlet. In addition to the default folders and files generated by the default template, we're going to create a folder named icons and a file under the folder icons named kb-admin. Add the JSP file, init.
Portlet definition First, we need to set up the portlet in the portlet. You can simply create an XML file portlet. Add the following lines of code at the beginning of portlet.
Also, most importantly, the default view name init-param must be view-jsp. Liferay portlet registration Next, we need to register the portlets.
To do so, create the XML file liferayportlet. Add the following lines at the beginning of liferay-portlet. It specifies the portlet name kb-admin-portlet by the tag portlet-name. Liferay portlet display Additionally, we expect to put the portlets in the category Knowledge Base. To do so, create an XML file liferay-display. Add the following lines at the beginning of liferay-display. Liferay plugin package Most importantly, you need to add a plugin properties file called liferay-pluginpackage.
Note that we can't include portal-impl. When deploying the plugin, the deploying process will generate the Liferay plugin package XML file liferay-plugin-package. View specification As seen in portlet. Thus, we need to create a JSP file named view.
First of all, let's bring the tags and predefined objects into the view. To do so, create a JSP file named init. Then, it brings in Portlet 2. Then, it brings the Liferay taglibs security prefix liferay-security , theme prefix liferay-theme , UI prefix liferay-ui , and utility prefix liferay-util. Finally, it includes two sets of defined objects: portlet:defineobjects and liferay-theme:defineobjects. For more details about these taglibs, refer to the book Liferay User Interface Development.
Next, add your custom code to view. The following is the sample code. You should have your own logic and view. In addition, the XML file liferayplugin-package.
The portlet-app element is the root of the deployment descriptor for a portlet application. This element has a required attribute version that specifies which version of the schema the deployment descriptor conforms to.
In order to be a valid JSR portlet application, the version must have the value 2. This name must be unique within the portlet application. At the same time, you should have a display name such as display-name and a portlet class such as portlet-class. Additionally, JSR specifies that the portlet preferences should be unique per user, by default. Liferay assumes that they are owned by a group that is, a site or an organization , by default. Liferay portlet app DTD The liferay-portlet-app element is the root of the deployment descriptor for a Liferay portlet application.
It can have zero or many elements, such as portlet, role-mapper, and custom-user-attribute. The custom-user-attribute contains a list of names that are retrieved using a custom class that extends com. This element can have one or many name, and only one custom-class.
The role-mapper contains two names specified by role-name and role-link. The role-name value must be a role specified in portlet. The role-link value must be the name of a Liferay role that exists in the database.
The role-mapper element pairs up these two values to map roles from portlet. And the? The portlet-name element contains the unique name of the portlet. This name must match the portlet name specified in portlet. You can set the value of the child element instanceable to true, if the portlet can appear multiple times on a page.
If set to false, the portlet can only appear once on a page. The default value is false. Within the child element css-class-wrapper, you can also set the name of the CSS class that will be injected in the DIV that wraps this portlet. If the element is set to true, the default portlet resources and permissions are added to the page. First, we introduce how to share web site, pages, or portlets with friends.
Then we introduce how to customize My Account and how to build My Street with personalized preferences.
It introduces how to build layout templates in Ext first. Then it discusses how to build layout templates and themes in Plugins SDK and how to add Velocity services in themes.
Finally, it addresses how to use Plugins SDK in an efficient way. We introduce Control Panel first—how it works and how to customize it.
Later, we discuss how to set up Social Office themes and portlets, and how to hook language properties, and portal properties. Finally, we discuss an efficient way to use hooking features.
In Chapter 11, we look at staging and publishing both locally and remotely, where we first discuss simple extension—how to build dynamic navigation and how to construct customized site map.
Then, we address how to handle events and model listeners. Based on these features, we further introduce local staging and publishing, and staging workflow. A way to schedule pages and assets is also discussed. Finally, we address how to publish the web content remotely, where portlet-data-handler for export and import via LAR is addressed as well. In Chapter 12, we first cover how to use custom attributes for both journal article templates and custom portlets.
Then, we address how to build OpenSearch and how to employ search capabilities. Later, we focus on approaches on how to employ Spring services and how to construct web services. What you need for this book This book uses Liferay portal version 5. Readers need to know the basics of Liferay and be competent Java developers. They should have some knowledge of the "standards" that Liferay adopts, but that's not so essential—we will try to explain the important ones in the book.
Although Liferay portal makes heavy use of open source frameworks such as Spring, Hibernate, Struts, and Lucene, no prior experience in using these is assumed. Here are some examples of these styles, and an explanation of their meaning. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "when the user enters an empty book title and clicks on the Add Book button, the error page depicts an error message: Error!
The Book Title is null! Warnings or important notes appear in a box like this. Tips and tricks appear like this. Let us know what you think about this book—what you liked or may have disliked.