<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Liferay on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/liferay/</link>
    <description>Recent content in Liferay on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Dec 2011 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/liferay/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Liferay Portlet Shell</title>
      <link>https://insinuator.net/2011/12/liferay-portlet-shell/</link>
      <pubDate>Wed, 21 Dec 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/12/liferay-portlet-shell/</guid>
      <description>&lt;p&gt;During one of our pentests in some corporate environment we were to analyze an application-server called &lt;a href=&#34;http://www.liferay.com&#34; title=&#34;Download Liferay Portlet Shell&#34;&gt;Liferay&lt;/a&gt;. Liferay comes with a lot of functionalities, runs on top of Apache Tomcat and includes a nice API that makes it very easy to add components or further functionality that are not part of the core. These (potentially selfmade) “addons” are called “portlets” and they can be inserted in any place in the frontend.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
