June 2010 - portal-commits - Jboss List Archives

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 08:17:57 -0400 (Wed, 30 Jun 2010) New Revision: 13953 Added: tags/Enterprise_Portal_Platform_4_3_GA_CP05/ Log: Tagging EPP 4.3 CP05 Copied: tags/Enterprise_Portal_Platform_4_3_GA_CP05 (from rev 13952, branches/Enterprise_Portal_Platform_4_3)

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13952 - examples/tags.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 08:10:09 -0400 (Wed, 30 Jun 2010) New Revision: 13952 Added: examples/tags/Enterprise_Portal_Platform_4_3_GA_CP05/ Log: Tagging examples Copied: examples/tags/Enterprise_Portal_Platform_4_3_GA_CP05 (from rev 13951, examples/trunk)

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13951 - docs/enterprise/trunk.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 07:31:58 -0400 (Wed, 30 Jun 2010) New Revision: 13951 Removed: docs/enterprise/trunk/4.3.cp05_Reference_Guide/ Log: Deleting a tag in a trunk...

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13950 - in docs/enterprise/trunk/Reference_Guide: en-US and 1 other directory.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 07:30:33 -0400 (Wed, 30 Jun 2010) New Revision: 13950 Added: docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.ent docs/enterprise/trunk/Reference_Guide/publican.cfg Removed: docs/enterprise/trunk/Reference_Guide/Makefile Modified: docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml docs/enterprise/trunk/Reference_Guide/en-US/Supported.xml Log: Preparing for CP05 release Deleted: docs/enterprise/trunk/Reference_Guide/Makefile =================================================================== --- docs/enterprise/trunk/Reference_Guide/Makefile 2010-06-30 09:58:36 UTC (rev 13949) +++ docs/enterprise/trunk/Reference_Guide/Makefile 2010-06-30 11:30:33 UTC (rev 13950) @@ -1,15 +0,0 @@ -#Makefile for JBoss_Portal_Reference_Guide - -XML_LANG = en-US -#DOCNAME = JBoss_Portal_Reference_Guide -BRAND = JBoss -#PRODUCT = Documentation - - -#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW -OTHER_LANGS = ja-JP -TRANSLATIONS = $(XML_LANG) $(OTHER_LANGS) - -COMMON_CONFIG = /usr/share/publican -include $(COMMON_CONFIG)/make/Makefile.common - Modified: docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml 2010-06-30 09:58:36 UTC (rev 13949) +++ docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml 2010-06-30 11:30:33 UTC (rev 13950) @@ -45,12 +45,13 @@ </section> <section id="configuration-cms_content"> <title>CMS content</title> + <para>Since 2.6 displaying CMS content in the portal is done using the new content integration feature. Each window of the portal can be configured to display CMS content directly instead of having to configure the CMS portlet as it used to be. </para> <section> <title>Configuring a window to display CMS content</title> - <para>Showing CMS content in a portal window can be done in the deployment descriptor quite easily + <para>Showing CMS content in a portal window can be done in the deployment descriptor quite easily</para> <programlisting><![CDATA[<window> <window-name>MyCMSWindow</window-name> <content> @@ -61,6 +62,7 @@ <height>1</height> </window> ]]></programlisting> + <para> At the first display of the window, the content is initialized with the content uri value. When the user clicks on a link that navigates to another CMS file, the CMS file will be shown in the same window. Added: docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.ent =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.ent (rev 0) +++ docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.ent 2010-06-30 11:30:33 UTC (rev 13950) @@ -0,0 +1,8 @@ +<!ENTITY PRODUCT "JBoss Portal"> +<!ENTITY JBEPPVERS "4.3"> +<!ENTITY BOOKID "Reference Guide"> +<!ENTITY YEAR "2010"> +<!ENTITY HOLDER "Red Hat"> + + + Modified: docs/enterprise/trunk/Reference_Guide/en-US/Supported.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Supported.xml 2010-06-30 09:58:36 UTC (rev 13949) +++ docs/enterprise/trunk/Reference_Guide/en-US/Supported.xml 2010-06-30 11:30:33 UTC (rev 13950) @@ -30,7 +30,7 @@ </section> <section> <title>JBoss Enterprise Application Platform (EAP)</title> - <para>Enterprise Portal Platform 4.3 CP03 embeds JBoss EAP 4.3_CP07 (That also contains Seam 2) and supports the same environment unless specified.</para> + <para>Enterprise Portal Platform 4.3 CP05 embeds JBoss EAP 4.3_CP08 (That also contains Seam 2) and supports the same environment unless specified.</para> </section> <section id="supportedversions-db"> <title>Databases</title> Added: docs/enterprise/trunk/Reference_Guide/publican.cfg =================================================================== --- docs/enterprise/trunk/Reference_Guide/publican.cfg (rev 0) +++ docs/enterprise/trunk/Reference_Guide/publican.cfg 2010-06-30 11:30:33 UTC (rev 13950) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Thu Dec 10 15:24:54 2009 + +debug: 1 +xml_lang: en-US +brand: JBoss + Property changes on: docs/enterprise/trunk/Reference_Guide/publican.cfg ___________________________________________________________________ Name: svn:executable + *

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13949 - docs/enterprise/trunk.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 05:58:36 -0400 (Wed, 30 Jun 2010) New Revision: 13949 Removed: docs/enterprise/trunk/Read_Me/ Log: Unused anymore

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13948 - docs/enterprise/trunk.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-30 05:57:57 -0400 (Wed, 30 Jun 2010) New Revision: 13948 Added: docs/enterprise/trunk/Release_Notes/ Removed: docs/enterprise/trunk/4.3.cp05_Release_Notes/ Log: Renamed Release Notes Copied: docs/enterprise/trunk/Release_Notes (from rev 13947, docs/enterprise/trunk/4.3.cp05_Release_Notes)

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13947 - docs/enterprise/trunk/Reference_Guide/en-US.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-29 08:58:00 -0400 (Tue, 29 Jun 2010) New Revision: 13947 Modified: docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml Log: JBEPP-158: Remove note about future JSR-286 support from EPP 4.3 docs Modified: docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml 2010-06-28 09:35:12 UTC (rev 13946) +++ docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml 2010-06-29 12:58:00 UTC (rev 13947) @@ -481,166 +481,6 @@ <para>That's it - we now have a user counter that will display it states each time a user logs-in our logs-out.</para> </section> <section> - <title>Achieving Inter Portlet Communication with the events mechanism</title> - <para>The first version of the Portlet Specification (JSR 168), regretfully, did not cover interaction between - portlets. The side-effect of diverting the issue to the subsequent release of the specification, has - forced portal vendors to each craft their own proprietary API to achieve inter portlet communication. Here we will - see how we can use the event mechanism to pass parameters from one portlet to the other (and only to the other portlet).</para> - <para>The overall scenario will be that Portlet B will need to be updated based on some parameter set on Portlet A. - To achieve that we will use a portal node event.</para> - <para>Portlet A is a simple Generic portlet that has a form that sends a color name: - <programlisting><![CDATA[ -public class PortletA extends GenericPortlet -{ - protected void doView(RenderRequest request, RenderResponse response) - throws PortletException, PortletSecurityException, IOException - { - response.setContentType("text/html"); - PrintWriter writer = response.getWriter(); - writer.println("<form action=\"" + response.createActionURL() + "\" method=\"post\">"); - writer.println("<select name=\"color\">"); - writer.println("<option>blue</option>"); - writer.println("<option>red</option>"); - writer.println("<option>black</option>"); - writer.println("</select>"); - writer.println("<input type=\"submit\"/>"); - writer.println("</form>"); - writer.close(); - } -} - ]]></programlisting> - </para> - <para>The other portlet (Portlet B) that will receive parameters from Portlet A is also a simple Generic portlet: - <programlisting><![CDATA[ -public class PortletB extends GenericPortlet -{ - - public void processAction(ActionRequest request, ActionResponse response) - throws PortletException, PortletSecurityException, IOException - { - String color = request.getParameter("color"); - if (color != null) - { - response.setRenderParameter("color", color); - } - } - - protected void doView(RenderRequest request, RenderResponse response) - throws PortletException, PortletSecurityException, IOException - { - String color = request.getParameter("color"); - response.setContentType("text/html"); - PrintWriter writer = response.getWriter(); - writer.println("<div" + - (color == null ? "" : " style=\"color:" + color + ";\"") + - ">some text in color</div>"); - writer.close(); - } - - // Inner listener explained after -} - ]]></programlisting> - </para> - <para>With those two portlets in hands, we just want to pass parameters from Portlet A to Portlet B (the color in - as a request parameter in our case). In order to achieve this goal, we will write an inner Listener in Portlet B - that will be triggered on any WindowActionEvent of Portlet A. This listener will create a new WindowActionEvent - on the window of Portlet B. - <programlisting role="java"><![CDATA[ -public static class Listener implements PortalNodeEventListener -{ - public PortalNodeEvent onEvent(PortalNodeEventContext context, PortalNodeEvent event) - { - PortalNode node = event.getNode(); - // Get node name - String nodeName = node.getName(); - // See if we need to create a new event or not - WindowActionEvent newEvent = null; - if (nodeName.equals("PortletAWindow") && event instanceof WindowActionEvent) - { - // Find window B - WindowActionEvent wae = (WindowActionEvent)event; - PortalNode windowB = node.resolve("../PortletBWindow"); - if (windowB != null) - { - // We can redirect - newEvent = new WindowActionEvent(windowB); - newEvent.setParameters(wae.getParameters()); - - newEvent.setMode(wae.getMode()); - newEvent.setWindowState(WindowState.MAXIMIZED); - - // Redirect to the new event - return newEvent; - } - } - // Otherwise bubble up - return context.dispatch(); - } -} - ]]></programlisting> - </para> - <para> - It is important to note here some of the important items in this listener class. - Logic used to determine if the requesting node was Portlet A.: - <programlisting>nodeName.equals("PortletAWindow")</programlisting> - </para> - <para> - Get the current window object so we can dispatch the event to it: - <programlisting>PortalNode windowB = node.resolve("../PortletBWindow");</programlisting> - </para> - <para> - Set the original parameter from Portlet A, so Portlet B can access them in its processAction(): - <programlisting>newEvent.setParameters(wae.getParameters());</programlisting> - </para> -  - <para> - We still need to register our listener as an mbean: - <programlisting role="xml"> -<![CDATA[<mbean - code="org.jboss.portal.core.event.PortalEventListenerServiceImpl" - name="portal:service=ListenerService,type=test_listener" - xmbean-dd="" - xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> - <xmbean/> - <depends - optional-attribute-name="Registry" - proxy-type="attribute">portal:service=ListenerRegistry</depends> - <attribute name="RegistryId">test_listener</attribute> - <attribute name="ListenerClassName"> - org.jboss.portal.core.samples.basic.event.PortletB$Listener - </attribute> -</mbean>]]></programlisting> - For node events, we also need to declare on which node we want to listen, this is done by modifying - the <literal>*-object.xml</literal> that defines your portal nodes. In this example we want to trigger - the listener each time the window containing the portlet A is actioned. We can add the <literal>listener</literal> - tag to specify that out listener with <literal>RegistryId</literal>=test_listener should be triggered - on events on the embedding object. - <programlisting> -<![CDATA[... - <window> - <window-name>PortletAWindow</window-name> - <instance-ref>PortletAInstance</instance-ref> - <region>center</region> - <height>0</height> - <listener>test_listener</listener> - </window> -...]]> - </programlisting> - Of course we could have added it at the page level instead of the window level. Note that a unique listener - can be specified, the event mechanism is primarily done to let the developer change the navigation state of the - portal, this example being a nice side-effect of this feature. - </para> - <note><para>The portlet 2.0 specification (JSR 286) will cover Inter Portlet Communication so that portlets using it - can work with different portal vendors.</para></note> - </section> - <section> <title>Link to other pages</title> <para>Linking to some other pages or portals is also out of the scope of the portlet specification. As seen previously JBoss Portal offers an API in order to create links

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13946 - branches/Enterprise_Portal_Platform_4_3/build.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-28 05:35:12 -0400 (Mon, 28 Jun 2010) New Revision: 13946 Modified: branches/Enterprise_Portal_Platform_4_3/build/build-thirdparty.xml Log: JBEPP-389: Upgrade to CMS 1.2.8 Modified: branches/Enterprise_Portal_Platform_4_3/build/build-thirdparty.xml =================================================================== --- branches/Enterprise_Portal_Platform_4_3/build/build-thirdparty.xml 2010-06-28 07:31:03 UTC (rev 13945) +++ branches/Enterprise_Portal_Platform_4_3/build/build-thirdparty.xml 2010-06-28 09:35:12 UTC (rev 13946) @@ -68,7 +68,7 @@ <componentref name="jboss-portal/modules/test" version="1.0.5"/> <componentref name="jboss-portal/modules/portlet" version="2.0.9"/> <componentref name="jboss-portal/modules/identity" version="1.1.2"/> - <componentref name="jboss-portal/modules/cms" version="1.2.7"/> + <componentref name="jboss-portal/modules/cms" version="1.2.8"/> <componentref name="antlr" version="2.7.6-brew"/> <componentref name="apache-ant" version="1.6.5"/> <componentref name="jackrabbit" version="1.4"/>

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13945 - in modules/cms/trunk: build and 1 other directories.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-28 03:31:03 -0400 (Mon, 28 Jun 2010) New Revision: 13945 Modified: modules/cms/trunk/build/pom.xml modules/cms/trunk/cms-jackrabbit/pom.xml modules/cms/trunk/pom.xml Log: Getting ready for next release Modified: modules/cms/trunk/build/pom.xml =================================================================== --- modules/cms/trunk/build/pom.xml 2010-06-28 07:29:40 UTC (rev 13944) +++ modules/cms/trunk/build/pom.xml 2010-06-28 07:31:03 UTC (rev 13945) @@ -18,7 +18,7 @@ <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.portal.cms</groupId> <artifactId>module-parent</artifactId> - <version>1.2.8</version> + <version>trunk-SNAPSHOT</version> <packaging>pom</packaging> <name>JBoss Portal CMS</name> <url>http://www.jboss.com/products/jbossmc</url> Modified: modules/cms/trunk/cms-jackrabbit/pom.xml =================================================================== --- modules/cms/trunk/cms-jackrabbit/pom.xml 2010-06-28 07:29:40 UTC (rev 13944) +++ modules/cms/trunk/cms-jackrabbit/pom.xml 2010-06-28 07:31:03 UTC (rev 13945) @@ -5,7 +5,7 @@ <groupId>org.jboss.portal.cms</groupId> <artifactId>module-parent</artifactId> <relativePath>../build/pom.xml</relativePath> - <version>1.2.8</version> + <version>trunk-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>cms-jackrabbit</artifactId> Modified: modules/cms/trunk/pom.xml =================================================================== --- modules/cms/trunk/pom.xml 2010-06-28 07:29:40 UTC (rev 13944) +++ modules/cms/trunk/pom.xml 2010-06-28 07:31:03 UTC (rev 13945) @@ -5,7 +5,7 @@ <artifactId>module-aggregator</artifactId> <packaging>pom</packaging> <name>JBoss Portal CMS Module</name> - <version>1.2.8</version> + <version>trunk-SNAPSHOT</version> <url>http://labs.jboss.com/jbossportal</url> <dependencies/>

13 years, 9 months

1
0
0 / 0

JBoss Portal SVN: r13944 - modules/cms/tags.

by portal-commits＠lists.jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-06-28 03:29:40 -0400 (Mon, 28 Jun 2010) New Revision: 13944 Added: modules/cms/tags/JBP_CMS_1_2_8/ Log: Tagging the CMS module Copied: modules/cms/tags/JBP_CMS_1_2_8 (from rev 13943, modules/cms/trunk)

13 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

portal-commits June 2010