From do-not-reply at jboss.org Tue May 31 05:44:41 2011 Content-Type: multipart/mixed; boundary="===============1267490631832332372==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: gatein-commits at lists.jboss.org Subject: [gatein-commits] gatein SVN: r6580 - in portal/trunk/docs/reference-guide/en-US/modules: PortletDevelopment and 1 other directory. Date: Tue, 31 May 2011 05:44:41 -0400 Message-ID: <201105310944.p4V9ifmr013210@svn01.web.mwc.hst.phx2.redhat.com> --===============1267490631832332372== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ndkhoiits Date: 2011-05-31 05:44:40 -0400 (Tue, 31 May 2011) New Revision: 6580 Added: portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment/Globa= l_portlet.xml Modified: portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment.xml Log: GTNPORTAL-1906 Update Reference Guide for Global Portlet feature Added: portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment/G= lobal_portlet.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment/Glob= al_portlet.xml (rev 0) +++ portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment/Glob= al_portlet.xml 2011-05-31 09:44:40 UTC (rev 6580) @@ -0,0 +1,95 @@ + + + %BOOK_ENTITIES; + ]> +
+ Global porlet.xml file +
+ Global portlet.xml usecase + The Portlet Specification introduces PortletFilter as a standa= rd approach to extend the behaviors of portlet + objects. For example, a filter can transform the content of port= let requests and portlet responses. + According to the Portlet Specification, normally there are three= steps in setting up a portlet filter: + + + + Implement a PortletFilter object + + + Define the filter in portlet application deployment de= scriptor + + + Define the filter mapping in portlet definitions + + + Two first steps are quite simple and easy to be done, however,= at the step 3, developers/administrators + need to replicate the filter mapping in many portlet definitions= , that makes work error and tedious in + several use cases. + The global portlet feature is designed to compensate such limita= tion. + +
+
+ Global metadata + The Global metadata is declared in the + portlet.xml file conformi= ng with Portlet 2.0 's XSD. + + <portlet-app version=3D"1.0"= xmlns=3D"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance&q= uot; + xsi:schemaLocation=3D"http://java.sun.com/xml/ns/portlet= /portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd= "> + +</portlet-app> +
+ Location + The path to the global portlet.xml is value of gatein.portlet.config in the configuration.properties = file and varied by hosting + application servers. + + For Tomcat: TOMCAT_HOME/gatein/conf/portlet.xml + For JBoss: JBOSS_HOME/server/default/conf/gatein/portlet.xml +
+
+ Global metadata elements + The global portlet.xml fi= le conforms to the schema of the portlet deployment descriptor defined in t= he Portlet + Specification with some restrictions. In this file, the follow= ing elements are supported: + + + + Portlet Filter + + + Portlet Mode + + + Window State + + +
+ Portlet filter + Portlet filter mappings declared in the global portlet.xml file are applied across portlet applica= tions. With + the XML configuration below, the filter ApplicationMonitor= ingFilter involves in request handling on any + deployed portlet. + + <filter> + <filter-name>org.exoplatform.portal.application.ApplicationMoni= toringFilter</filter-name> + <filter-class>org.exoplatform.portal.application.ApplicationMoni= toringFilter</filter-class> + <lifecycle>ACTION_PHASE</lifecycle> + <lifecycle>RENDER_PHASE</lifecycle> + <lifecycle>EVENT_PHASE</lifecycle> + <lifecycle>RESOURCE_PHASE</lifecycle> +</filter> + + Application Monitoring Filter + supports four lifecycle phases as the order below: + ACTION_PHASE/ EVENT_PHASE/ RENDER_= PHASE/ RESOURCE_PHASE + and + records statistic information on deployed portlets. + The filter alternates actual monitoring mechanism in WebUI F= ramework. + +
+
+ Portlet Mode and Window State + The global portlet.xml = file is considered as an alternative place to declare custom Portlet Modes = and Window States. + +
+
+
+
Modified: portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopmen= t.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment.xml = 2011-05-30 17:28:39 UTC (rev 6579) +++ portal/trunk/docs/reference-guide/en-US/modules/PortletDevelopment.xml = 2011-05-31 09:44:40 UTC (rev 6580) @@ -6,7 +6,8 @@ Portlet development = - + + = = --===============1267490631832332372==--