Author: woonsan
Date: Wed Nov 26 00:55:07 2014
New Revision: 1641740
URL: http://svn.apache.org/r1641740
Log:
APA-67: introduction to apa-webcontent2
Modified:
portals/site/applications/src/site/xdoc/webcontent2/index.xml
Modified: portals/site/applications/src/site/xdoc/webcontent2/index.xml
URL:
http://svn.apache.org/viewvc/portals/site/applications/src/site/xdoc/webcontent2/index.xml?rev=1641740&r1=1641739&r2=1641740&view=diff
==============================================================================
--- portals/site/applications/src/site/xdoc/webcontent2/index.xml (original)
+++ portals/site/applications/src/site/xdoc/webcontent2/index.xml Wed Nov 26
00:55:07 2014
@@ -41,11 +41,54 @@
</div>
<p>
A servlet/portlet application framework dedicated to the development
of reverse proxying,
- web content rewriting and IFrame based web content rendering.
- The servlet/filter modules are designed to serve remote web content
based on path mappings,
- and the portlet modules are designed to serve web content inside
portlet windows.
+ web content rewriting and rendering.
+ </p>
+ <p>
+ Apache Portals Web Content Application 2 consists of four submodules:
+ <strong>content-rewriter</strong>, <strong>reverse-proxy</strong>,
<strong>portlets</strong> and <strong>war</strong> package,
+ which can support various use cases.
+ </p>
+ <p>
+ For example, you may want to use <strong>reverse-proxy</strong> module
only
+ without having to use <strong>portlets</strong> or
<strong>war</strong> package modules
+ if you want to construct a reverse proxy service for your backend web
site, REST services, web services, etc.
+ Or you can use <strong>portlets</strong> module when you want to build
a new portlet application without having
+ to pull in the example configurations from <strong>war</strong>
package module.
+ </p>
+ <p>
+ The <strong>content-rewriter</strong> module defines a simple API and
implements simple components
+ to bridge various content rewriting framework such as text line based
rewriting or
+ <a href="http://htmlcleaner.sourceforge.net/";
target="_blank">HtmlCleaner</a>
+ based advanced rewriting.
+ </p>
+ <p>
+ The <strong>reverse-proxy</strong> module defines HTTP <a
href="http://en.wikipedia.org/wiki/Reverse_proxy";>Reverse Proxy</a> application
framework for servlets or filters,
+ providing <a href="http://yaml.org/spec/1.1/";>YAML</a> based proxy
path mapping configurations and default content rewriter components.
+ </p>
+ <p>
+ The <strong>portlets</strong> module consists of various portlets
serving remote content
+ through either server-side HTTP Client handling or IFrame-based
client-side page handling.
+ </p>
+ <p>
+ The <strong>war</strong> package module has all of the other modules
with example configurations
+ for servlets, filters, portlets and others.
+ </p>
+ <p>Please see <a href="modules-overview.html">Modules Overview</a> page
for detail.</p>
+ <p>
+ <strong><em>Note: </em></strong>
+ Apache Portals Web Content Application 2 was rewritten from the
previous versions
+ in order to take advantage of the newer version of
+ <a href="http://hc.apache.org/"; target="_blank">Apache
HttpComponents</a>
+ and to be more flexible as a framework, especially for
content-rewriting and reverse-proxying.
+ For example, it used to try to provide every feature in the default
reverse proxy component in the previous versions,
+ but it now tries to provide a more flexible framework based on
+ <a href="http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern";
target="_blank">Chain of Responsibility pattern</a>
+ (using <a href="http://commons.apache.org/proper/commons-chain/";
target="_blank">Apache Commons Chain</a>) instead.
+ So, it uses a different package
(org.apache.portals.applications.webcontent2)
+ than the previous versions
(org.apache.portals.applications.webcontent),
+ allowing it to be used at the same time as an earlier version.
+ As a result, it is incompatible with the previous versions.
</p>
-
</section>
</body>
