
errata for the liferay user interface development
Liferay Book: Liferay User Interface Development
Liferay Book: Liferay User Interface Development
Customizing your Liferay Portal #
Page 21 and enjoyable experience should be an enjoyable experience
Basic Theme Development #
Page 56 init_cutom.vm should be init_custom.vm
From page 37 through page 55
palm-tree-publications-theme
should be
palmtree-theme
Layouts Templates #
Page 118 access to the it should be access to it
Page 131 brower should be browser
Styling Pages #
Advanced Theme #
Portlet User Interface #
Velocity Templates #
Alloy User Interface #
UI Taglib #
User Interface in Production #
on page 333,
"As you have been noticed, six kinds of plugins are available in Liferay - they are portlets, themes, layout templates, hooks, Ext plugins, and web application integrator (short for WAI, or called webs)."
should be
"As you have been noticed, six kinds of plugins are available in Liferay - they are portlets, themes, layout templates, hooks, Ext plugins, and web applications (called webs)."
and
"The Web Application Integrator (WAI) will automatically deploy any standard Java servlet application as a portlet within Liferay.WAI (or called webs) is a pure web app where thin layer was added to provide checking for dependencies. A web-plugin does add support for embedding hook definition or Service Builder services within a plain web app. To use the WAI, you can simply copy an application WAR file into the auto-deploy directory, and then add the portlet to your page. The portal transparently handles the rest."
should be
The Web Application Integrator (WAI), a special web plugin, will automatically deploy any standard Java servlet application as a portlet within Liferay. A web plugin is a pure web app where thin layer was added to provide checking for dependencies. A web-plugin does add support for embedding hook definition or Service Builder services within a plain web app. To use the webs (or especially WAI), you can simply copy an application WAR file into the auto-deploy directory, and then add the portlet to your page. The portal transparently handles the rest.