Similarly to creating a portlet you start by typing
Liferay is the most widely used open source portal products in the market. There are different version of Liferay available in the market both in community and enterprise editions. + Version 1.0+ + Version 4.0+ + Version 5.0+ + Version 6.0+ The version I am working on is version 5.2.3 community of Liferay. Need help to setup Liferay 5.2.3 CE for development. Punam Shah has already given the download links on sourceforge - that's all you need.
and you should see a list of available archetypes starting with
Type 4 and press enter to choose “liferay-hook-archetype”. You will be asked to enter groupId, artifactId, version and package and then confirm. For example:
Once you confirm this data, a new folder (with name equal to the value of artifactId) will be created.
You can notice the directory structure:
There are only liferay-hook.xml and liferay-plugin-package.properties files. The hook is standard web application with these rules:
1, It contains liferay-plugin-package.properties
2, It contains liferay-hook.xml
3, The war file name contains “-hook” string
4, The war file name doesn’t contain “-portlet” string
1, It contains liferay-plugin-package.properties
2, It contains liferay-hook.xml
3, The war file name contains “-hook” string
4, The war file name doesn’t contain “-portlet” string
The content of the package is defined in the liferay-hook.xml, where I added some info on how to create hooks and what is supported in the Liferay 5.2.3:
For the right content of this file see
http://www.liferay.com/dtd/liferay-hook_5_1_0.dtd
http://www.liferay.com/dtd/liferay-hook_5_2_0.dtd
http://www.liferay.com/dtd/liferay-hook_5_1_0.dtd
http://www.liferay.com/dtd/liferay-hook_5_2_0.dtd
For the Liferay 5.2.3 use only:
<!ELEMENT portal-properties (#PCDATA)>
– .properties file should go into the src/main/resources directory
– supported keys in the .properties file:
“auth.forward.by.last.path”,
“captcha.check.portal.create_account”,
“default.landing.page.path”,
“field.enable.com.liferay.portal.model.Contact.birthday”,
“field.enable.com.liferay.portal.model.Contact.male”,
“field.enable.com.liferay.portal.model.Organization.status”,
“javascript.fast.load”,
“layout.static.portlets.all”
“layout.template.cache.enabled”,
“layout.user.private.layouts.auto.create”,
“layout.user.private.layouts.enabled”,
“layout.user.private.layouts.modifiable”,
“layout.user.public.layouts.auto.create”,
“layout.user.public.layouts.enabled”,
“layout.user.public.layouts.modifiable”,
“login.create.account.allow.custom.password”,
“my.places.show.community.private.sites.with.no.layouts”,
“my.places.show.community.public.sites.with.no.layouts”,
“my.places.show.organization.private.sites.with.no.layouts”,
“my.places.show.organization.public.sites.with.no.layouts”,
“my.places.show.user.private.sites.with.no.layouts”,
“my.places.show.user.public.sites.with.no.layouts”,
“passwords.passwordpolicytoolkit.generator”,
“passwords.passwordpolicytoolkit.static”
“terms.of.use.required”,
“theme.css.fast.load”,
“theme.images.fast.load”
<!ELEMENT language-properties (#PCDATA)><!ELEMENT portal-properties (#PCDATA)>
– .properties file should go into the src/main/resources directory
– supported keys in the .properties file:
“auth.forward.by.last.path”,
“captcha.check.portal.create_account”,
“default.landing.page.path”,
“field.enable.com.liferay.portal.model.Contact.birthday”,
“field.enable.com.liferay.portal.model.Contact.male”,
“field.enable.com.liferay.portal.model.Organization.status”,
“javascript.fast.load”,
“layout.static.portlets.all”
“layout.template.cache.enabled”,
“layout.user.private.layouts.auto.create”,
“layout.user.private.layouts.enabled”,
“layout.user.private.layouts.modifiable”,
“layout.user.public.layouts.auto.create”,
“layout.user.public.layouts.enabled”,
“layout.user.public.layouts.modifiable”,
“login.create.account.allow.custom.password”,
“my.places.show.community.private.sites.with.no.layouts”,
“my.places.show.community.public.sites.with.no.layouts”,
“my.places.show.organization.private.sites.with.no.layouts”,
“my.places.show.organization.public.sites.with.no.layouts”,
“my.places.show.user.private.sites.with.no.layouts”,
“my.places.show.user.public.sites.with.no.layouts”,
“passwords.passwordpolicytoolkit.generator”,
“passwords.passwordpolicytoolkit.static”
“terms.of.use.required”,
“theme.css.fast.load”,
“theme.images.fast.load”
- .properties file should go into the src/main/resources directory
- if you specify WEB-INF/your-directory-name then the directory with JSPs should go into the src/main/webapp/WEB-INF/your-directory-name
<!ELEMENT model-listener (model-listener-class, model-name)>- the java classes should go into the src/main/java directory
<!ELEMENT event (event-class, event-type)>- the java classes should go into the src/main/java directory
Private | |
Industry | Software |
---|---|
Founded | 2004 |
Headquarters | , |
Products | Liferay Portal Liferay Commerce Liferay Analytics Cloud |
Website | www.liferay.com |
Liferay, Inc., is an open-source company that provides free documentation and paid professional service to users of its software. Mainly focused on enterprise portal technology, the company has its headquarters in Diamond Bar, California, United States.
History[edit]
Liferay's original product, Liferay Portal, was created in 2000 by chief software architect Brian Chan to provide an enterprise portal solution[buzzword] for non-profit organizations.[1] In 2004, the company was incorporated under the name Liferay, Inc. and formalized its Germany subsidiary Liferay GmbH. In 2007, the company opened a new Asian headquarters in Dalian, China, and the Spanish subsidiary Liferay SL. In March 2009, the company opened a new office in Bangalore, India. To date Liferay has 22 offices worldwide [2] with over 250 partners [3] and 180,000 open source community members.[citation needed]
Sun Microsystems and Liferay signed a technology-sharing agreement during May 2008.[4] Sun Microsystems rebranded the offering GlassFish Web Space Server. ZDNet further describes the relationship in the May 2008 article Sun and Liferay launch web-presentation platform.[5] In 2010 Sun was acquired by Oracle[6] and the GlassFish Web Space Server was not included in their portal roadmap, with all prospects turned over to Liferay, Inc.
In April 2013, Liferay partnered with TIBCO Software to offer a series of Liferay enterprise Connectivity Adapters (eC Adapters) that use TIBCO ActiveMatrix BusinessWorks with the intention of easing integration of Liferay Portal with multiple systems.[7]
In May 2016, the company introduced Liferay Digital Experience Platform, an expansion of the original Liferay Portal, to offer additional functionality such as engagement metrics.[8]
In July 2018, Liferay released two new products: a B2B focused digital commerce solution[buzzword] named Liferay Commerce, and a cloud analytics software called Liferay Analytics Cloud.[9]
See also[edit]
References[edit]
- ^Howard, Phil (October 18, 2005). 'Liferay after Plumtree: Pure play portals alive and kicking'. Reg Developer.
- ^'About Us / Locations'. July 2018.
- ^'Liferay Partners'. July 2018.
- ^'Press Release: Sun Joins Liferay Open Source Community'. May 2008.
- ^'Sun and Liferay launch web-presentation platform'. May 2008.
- ^'Oracle buys Sun, becomes hardware company'. January 27, 2010.
- ^'Enterprise Portal Liferay Partners with TIBCO Software for Lower Cost Back-End Integration'. www.cmswire.com. Retrieved 2013-04-30.
- ^'Press Release - Liferay'. www.liferay.com.
- ^Jackson, Brian. 'Liferay leaps into digital customer experience market, seeks growth in Canada'. IT World Canada.
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Liferay&oldid=930482392'