November 2011 - gatein-commits - Jboss List Archives

gatein SVN: r8069 - in epp/docs/branches/5.2: Site_Publisher/Release_Notes and 1 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-11-14 23:07:35 -0500 (Mon, 14 Nov 2011) New Revision: 8069 Added: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml Removed: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/need_info.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/not_documented.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg Log: Release Notes amendments for EPP 5.2.0 Beta Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_BETA_Release_Notes.ent"> %BOOK_ENTITIES; ]> <book> @@ -49,9 +49,7 @@ </note> </chapter> <chapter id="Release_Notes-Component_Features"> - <title> - Component Versions - </title> + <title>Component Versions </title> <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> <table frame="all" pgwide="1"> <title>Component Versions</title> @@ -191,17 +189,13 @@ </para> </chapter> <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title> - Resolved Issues - </title> + <title>Resolved Issues </title> <para> The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> </chapter> <chapter id="Release_Notes-Known_Issues"> - <title> - Known Issues - </title> + <title>Known Issues </title> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> </chapter>  <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1224"/> - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is OPEN</remark> - <para> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1224" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> The Services Management Gadget currently has a display issue with the tabs displaying to the left of the table containing the data. This problem presented on Microsoft Internet Explorer 7 on Windows Vista. A fix is being investigated. </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1236"/> - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is OPEN</remark> - <para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1236" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + org.exoplatform.services.cache.impl.jboss.ExoCacheFactoryImpl.createCache runs for both clustered and non-clustered environments. This class registers JBoss Cache to JMX, which produces MBeans for clustered services regardless of whether the clustered services are actively used in the environment. A fix is being investigated. </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1258"/> - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is OPEN</remark> - <para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1258" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> Some CSS issues have been identified with the way the Portal home page is rendered. A fix is being investigated. </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1271"/> - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is OPEN</remark> - <para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1271" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> When adding a portlet into a 2-column layout container, the container collapses while dragging the portlet into the container. The container sometimes remains collapsed after moving the portlet into the container. This problem presented on Microsoft Windows 7, using Internet Explorer 8. A fix is being investigated. </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1345"/> - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is OPEN</remark> - <para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1345" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> An interface abnormality was discovered in the Account Portlet. If more than one instance of the Account Portlet is present on a page, tabs switching will work in the first portlet as designed. If tab switching is attempted in the other instances, the tab and the content in the portlet flashes temporarily, and the original tab is shown again. A fix is being investigated. </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1351"/> - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is OPEN</remark> - <para> - The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module does not have these options. This causes problems when a customer wants to implement SSO on a different portal container (for example in ecmdemo). No workaround exists for this issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1359"/> - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is OPEN</remark> - <para> + + </listitem> + </varlistentry> + + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1359" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> Sybase 15.5 imposes a limitation on the case used in portal names. Only lowercase portal names are supported. The problem does not present in Sybase 15.0.3. A fix is being investigated. </para> - </listitem> - </varlistentry> + + </listitem> + </varlistentry> + </variablelist> Modified: epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,47 +1,68 @@ -<?xml version='1.0' encoding='UTF-8'?> +<?xml version='1.0'?> <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> + + <variablelist> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-729"/> - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is OPEN</remark> - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-729" /></term> + <listitem> + + <remark>Assignee is: mposolda</remark> + + + <remark>JIRA is OPEN</remark> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> </para> - </warning> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1125"/> - </term> - <listitem> - <remark>Assignee is: prabhat.jha</remark> - <remark>JIRA is OPEN</remark> - <para> + </warning> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1125" /></term> + <listitem> + + <remark>Assignee is: prabhat.jha</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1324"/> - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is OPEN</remark> - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1324" /></term> + <listitem> + + <remark>Assignee is: hfnukal</remark> + + + <remark>JIRA is OPEN</remark> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> </para> - </warning> - </listitem> - </varlistentry> + </warning> + + </listitem> + </varlistentry> + </variablelist> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,18 +1,19 @@ <?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE articleinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_Release_Notes.ent"> %BOOK_ENTITIES; ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>Site Publisher 5.2.0 Release Notes</title> - <subtitle>For the JBoss Enterprise Portal Platform Site Publisher &VZ; extension.</subtitle> + <title>Site Publisher 5.2.0 BETA Release Notes</title> + <subtitle>For the JBoss Enterprise Portal Platform Site Publisher extension.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>3</pubsnumber> + <pubsnumber>4</pubsnumber> <abstract> <para> - These release notes contain important information related to JBoss Site Publisher &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. + These release notes contain important information related to JBoss Site Publisher that may not be currently available in the Product Manuals. + You should read these Release Notes in their entirety before installing the product. </para> </abstract> <corpauthor> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -8,8 +8,8 @@ <simpara> <revhistory> <revision> - <revnumber>5.2.0-3</revnumber> - <date>Wed Nov 9 2011</date> + <revnumber>5.2.0-4</revnumber> + <date>Tue Nov 15 2011</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> @@ -17,38 +17,10 @@ </author> <revdescription> <simplelist> - <member>Converted from Article to Book, to enable better TOC and structure.</member> + <member>Release Notes prepared for Enterprise Portal Platform Site Publisher 5.2.0 Beta.</member> </simplelist> </revdescription> </revision> - <revision> - <revnumber>5.2.0-2</revnumber> - <date>Wed Nov 9 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Bumped for cvs branching.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>5.2.0-1</revnumber> - <date>Mon Aug 29 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Updating version and resetting pubs/ed numbers.</member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Copied: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent (from rev 8056, epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent) =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent 2011-11-15 04:07:35 UTC (rev 8069) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Site Publisher"> + + +<!ENTITY BOOKID "Site Publisher Release Notes"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "5"> +<!ENTITY VY "5.2"> +<!ENTITY VZ "5.2.0"> Copied: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml (from rev 8056, epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml) =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -0,0 +1,156 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_BETA_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <chapter id="Release_Notes-Introduction"> + <title>Introduction</title> + <para> + JBoss Site Publisher (powered by eXo) is an add-on component for JBoss Enterprise Portal Platform. Site Publisher enables users to create, edit and publish rich web content within the context of their portal installation. + </para> + <note> + <title>Subscription</title> + <para> + Subscriptions to JBoss Site Publisher are available at an additional fee over and above JBoss Enterprise Portal Platform subscriptions. + </para> + </note> + <para> + JBoss Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content: + </para> + <itemizedlist> + <listitem> + <para> + Webmasters can easily administer multiple websites. + </para> + </listitem> + <listitem> + <para> + Website administrators can set permission policies according to user roles to better control website changes. + </para> + </listitem> + <listitem> + <para> + Content providers can use JBoss Enterprise Portal Platform’s tools to create content and then choose how to publish it using blogs, RSS feeds, social networks and more. + </para> + </listitem> + <listitem> + <para> + Web developers can introduce other forms of rich media content to create truly professional websites easily and efficiently. + </para> + </listitem> + </itemizedlist> + </chapter> + <chapter id="Release_Notes-Component_Features"> + <title>Component Features</title> + <formalpara> + <title>New Components</title> + <para>The following new components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>In-line Editing</term> + <listitem> + <para>This updated functionality enables content authors to modify existing web content upon the page in which it is presented. All an author needs to do is double click on the content to launch the content editor within the page. </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Search Engine Optimization (SEO)</term> + <listitem> + <para>A new interface for content authors provides a means to enter information to promote pages to different search engines and manage SEO settings on each page of the site. </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Updated Authoring Interface</term> + <listitem> + <para>The authoring interface has been update to be more intuitive for content authors to more quickly and easily create and manage their content. </para> + </listitem> + </varlistentry> + </variablelist> + </chapter> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Site Publisher <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_In_Production"> + <title>Issues Resolved In Production</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_Upstream"> + <title>Issues Resolved Upstream</title> + <para>This release contains Site Publisher issues resolved upstream by eXo Platform. These issues have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title>Known Issues</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml"/> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. + </para> + </chapter> + <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> + <title> Product Support and License Website Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Support Processes</title> + <para> + <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> + <title> Production Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> + <title> Production Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> + <title> Developer Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> + <title> Developer Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> + <title> Product Update and Support Policy by Product </title> + <para> + <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title> JBoss End User License Agreement </title> + <para> + <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> + </para> + </formalpara> + </chapter> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book> Deleted: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,14 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Site Publisher"> - - -<!ENTITY BOOKID "Site Publisher Release Notes"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.0"> Deleted: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,157 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> - -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_Release_Notes.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <chapter id="Release_Notes-Introduction"> - <title>Introduction</title> - <para> - JBoss Site Publisher (powered by eXo) is a new add-on component for JBoss Enterprise Portal Platform. Site Publisher enables users to create, edit and publish rich web content within the context of their portal installation. - </para> - <note> - <title>Subscription</title> - <para> - Subscriptions to JBoss Site Publisher are available at an additional fee over and above JBoss Enterprise Portal Platform subscriptions. - </para> - </note> - <para> - JBoss Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content: - </para> - <itemizedlist> - <listitem> - <para> - Webmasters can easily administer multiple websites. - </para> - </listitem> - <listitem> - <para> - Website administrators can set permission policies according to user roles to better control website changes. - </para> - </listitem> - <listitem> - <para> - Content providers can use JBoss Enterprise Portal Platform’s tools to create content and then choose how to publish it using blogs, RSS feeds, social networks and more. - </para> - </listitem> - <listitem> - <para> - Web developers can introduce other forms of rich media content to create truly professional websites easily and efficiently. - </para> - </listitem> - </itemizedlist> - </chapter> - <chapter id="Release_Notes-Component_Features"> - <title> - <remark>Component Features</remark> - </title> - <variablelist> - <varlistentry> - <term>Waiting...</term> - <listitem> - <para> - ...on content. - </para> - </listitem> - </varlistentry> - </variablelist> - </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Site Publisher Installation Guide contains detailed installation instructions as well as environment requirements. - </para> - <para> - The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title> - <remark>Issues Resolved In Production</remark> - </title> - <para> - The following issues were resolved in the production process of Site Publisher: - </para> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_Upstream"> - <title>Issues Resolved Upstream</title> - <para> - Awaiting triage efforts. - </para> - </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title> - <remark>Known Issues</remark> - </title> - <para> - Awaiting triage efforts. - </para> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An Installation Guide and a User Guide for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. - </para> - </chapter> - <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product Support and License Website Links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Support Processes</title> - <para> - <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> - <title> Production Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> - <title> Production Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> - <title> Developer Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> - <title> Developer Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> - <title> Product Update and Support Policy by Product </title> - <para> - <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title> JBoss End User License Agreement </title> - <para> - <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> - </para> - </formalpara> - </chapter> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,4 +1,29 @@ - -<para> -There are no known issues in this release. -</para> +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<variablelist> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1029"/> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is OPEN</remark> + <para> + It is not possible to add custom javascript to Site Publisher managed websites. While customers can inject custom CSS into their pages, javascript injection is not available. A fix is being investigated. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1362"/> + </term> + <listitem> + <remark>Assignee is: jaredmorgs</remark> + <remark>JIRA is OPEN</remark> + <para> + A problem has been identified with adding roles as the root user using the User and Group Management interface, when following the instructions in http://community.jboss.org/wiki/GateInwithLDAPinreadonlymode. Investigation is ongoing. + </para> + </listitem> + </varlistentry> +</variablelist> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/need_info.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/need_info.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/need_info.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,10 +1,4 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -<variablelist> - - - -</variablelist> +<para> +There are no issues that require more information at this time. +</para> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/not_documented.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/not_documented.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/not_documented.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,326 +1,3 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - - -<variablelist> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-612" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-633" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-647" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-648" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-680" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-684" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-704" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-748" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-749" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-750" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-755" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-756" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-758" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-759" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-792" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <para> - - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-963" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-979" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <para> - - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-990" /></term> - <listitem> - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -</variablelist> +<para> +All Issues are documented. +</para> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml 2011-11-15 04:07:35 UTC (rev 8069) @@ -1,73 +1,4 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -<variablelist> -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-645" /></term> - <listitem> - - - <para> - A bug in the Content Duplicity Check in the multiple content selector has been corrected. The content selector now matches the target path of each selected node against those already selected and, if a duplicate is found a warning is presented and the new node is rejected. This prevents users from selecting the same file more than once. - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-745" /></term> - <listitem> - - - <para> - An 'Unknown error' encountered when attempting to save an HTML page has been resolved in this release. - </para> - - </listitem> - </varlistentry> - - - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-751" /></term> - <listitem> - - - <para> - Problems with URL parameters being lost when returning from in-context editing in the ContentExplorer portlet were encountered in previous versions of JBoss Enterprise Portal Platform. This issue has been resolved in this release. - </para> - - </listitem> - </varlistentry> - - - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-947" /></term> - <listitem> - - - <para> - In previous versions of JBoss Enterprise Portal Platform, the Quick Login links found on the front page of the classic site where rendered inactive when the Site Publisher plugin was deployed. This issue has been corrected in this release. - </para> - - </listitem> - </varlistentry> - - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-957" /></term> - <listitem> - - - <para> - A bug in the Site Publisher code prevents the system from correctly calculating the size of an upload. This may allow files that do not adhere to the 10MB size limit to be uploaded. - </para> - - </listitem> - </varlistentry> - -</variablelist> +<para> +There are no resolved issues in this release. +</para> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-11-15 03:40:43 UTC (rev 8068) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-11-15 04:07:35 UTC (rev 8069) @@ -4,7 +4,7 @@ xml_lang: en-US type: Book brand: JBoss -show_remarks: 1 +#show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist -cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_5.2.0_Release_Notes-5.2-web-__LANG__ +cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_5.2.0_BETA_Release_Notes-5.2-web-__LANG__

13 years, 2 months

1
0
0 / 0

gatein SVN: r8068 - epp/portal/branches/EPP_5_1_0_GA_JBEPP-1346/web/eXoResources/src/main/webapp/javascript/eXo/core.

by do-not-reply＠jboss.org

Author: ghjboss Date: 2011-11-14 22:40:43 -0500 (Mon, 14 Nov 2011) New Revision: 8068 Modified: epp/portal/branches/EPP_5_1_0_GA_JBEPP-1346/web/eXoResources/src/main/webapp/javascript/eXo/core/Browser.js Log: fix for JBEPP-1346 Modified: epp/portal/branches/EPP_5_1_0_GA_JBEPP-1346/web/eXoResources/src/main/webapp/javascript/eXo/core/Browser.js =================================================================== --- epp/portal/branches/EPP_5_1_0_GA_JBEPP-1346/web/eXoResources/src/main/webapp/javascript/eXo/core/Browser.js 2011-11-15 03:36:33 UTC (rev 8067) +++ epp/portal/branches/EPP_5_1_0_GA_JBEPP-1346/web/eXoResources/src/main/webapp/javascript/eXo/core/Browser.js 2011-11-15 03:40:43 UTC (rev 8068) @@ -287,6 +287,9 @@ this.getBrowserWidth = function() { return document.body.clientWidth ; } + this.eventListener = function(object, event, operation) { object.addEventListener(event, operation, false) ; } + this.setOpacity = function(component, value) { component.style.opacity = value/100 ; } + this.getEventSource = function(e) { return e.target ; } } ; Browser.prototype.isIE6 = function() {

13 years, 2 months

1
0
0 / 0

gatein SVN: r8067 - epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-14 22:36:33 -0500 (Mon, 14 Nov 2011) New Revision: 8067 Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/date-property-comparison.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-descendant-nodes.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/offset-and-limit.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/or-constraint.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/order-by-score.xml Log: Checking in current state prior to modifying for stage for beta. Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/date-property-comparison.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/date-property-comparison.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/date-property-comparison.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -5,81 +5,42 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison"> <title>Date Property Comparison</title> - <para> - Find all nodes of primary type "nt:resource" whose jcr:lastModified property value is greater than 2006-06-04 and less than 2008-06-04. - </para> + <formalpara> + <title>Task:</title> + <para> + Find all nodes of primary type <literal>nt:resource</literal> whose <parameter>jcr:lastModified</parameter> property value is greater than <literal>2006-06-04</literal> and less than <literal>2008-06-04</literal>. + </para> + </formalpara> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Repository_Structure"> <title>Repository Structure</title> <para> - Repository contains nt:resource nodes with different values of jcr:lastModified property + Repository contains <literal>nt:resource</literal> nodes with different values of <parameter>jcr:lastModified</parameter> property. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (nt:file) - </para> - <itemizedlist> - <listitem> - <para> - jcr:content (nt:resource) jcr:lastModified="2006-01-19T15:34:15.917+02:00" - </para> +<programlisting>root + ├── document1 (nt:file) + │ └── jcr:content (nt:resource) jcr:lastModified="2006-01-19T15:34:15.917+02:00" + ├── document2 (nt:file) + │ └── jcr:content (nt:resource) jcr:lastModified="2005-01-19T15:34:15.917+02:00" + └── document3 (nt:file) + └── jcr:content (nt:resource) jcr:lastModified="2007-01-19T15:34:15.917+02:00" +</programlisting> - </listitem> - - </itemizedlist> - - </listitem> - <listitem> - <para> - document2 (nt:file) - </para> - <itemizedlist> - <listitem> - <para> - jcr:content (nt:resource) jcr:lastModified="2005-01-19T15:34:15.917+02:00" - </para> - - </listitem> - - </itemizedlist> - - </listitem> - <listitem> - <para> - document3 (nt:file) - </para> - <itemizedlist> - <listitem> - <para> - jcr:content (nt:resource) jcr:lastModified="2007-01-19T15:34:15.917+02:00" - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Query_Execution"> <title>Query Execution</title> - <para> - <emphasis role="bold">SQL</emphasis> + <formalpara> + <title>SQL</title> + <para> + In SQL you have to use the keyword <emphasis>TIMESTAMP</emphasis> for date comparisons. Otherwise, the date would be interpreted as a string. + </para> + </formalpara> + <para> + The date has to be surrounded by single quotes (<literal>TIMESTAMP 'datetime'</literal>) and in the ISO standard format: YYYY-MM-DDThh:mm:ss.sTZD. </para> - <para> - In SQL you have to use the keyword <emphasis role="bold">TIMESTAMP</emphasis> for date comparisons. Otherwise, the date would be interpreted as a string. The date has to be surrounded by single quotes (TIMESTAMP 'datetime') and in the ISO standard format: YYYY-MM-DDThh:mm:ss.sTZD ( <ulink url="http://en.wikipedia.org/wiki/ISO_8601">http://en.wikipedia.org/wiki/ISO_8601</ulink> and well explained in a W3C note <ulink url="http://www.w3.org/TR/NOTE-datetime">http://www.w3.org/TR/NOTE-datetime</ulink>). + <para> + Refer to <ulink url="http://en.wikipedia.org/wiki/ISO_8601">http://en.wikipedia.org/wiki/ISO_8601</ulink> or <ulink url="http://www.w3.org/TR/NOTE-datetime">http://www.w3.org/TR/NOTE-datetime</ulink> to more information. </para> <para> You will see that it can be a date only (YYYY-MM-DD) but also a complete date and time with a timezone designator (TZD). @@ -101,12 +62,13 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - <para> - Compared to the SQL format, you have to use the keyword <emphasis role="bold">xs:dateTime</emphasis> and surround the datetime by extra brackets: xs:dateTime('datetime'). The actual format of the datetime also conforms with the ISO date standard. - </para> + + <formalpara> + <title>XPath</title> + <para> + Compared to the SQL format, you have to use the keyword <emphasis>xs:dateTime</emphasis> and surround the datetime by extra brackets: <literal>xs:dateTime('datetime')</literal>. The actual format of the datetime also conforms with the ISO date standard. + </para> + </formalpara> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); @@ -128,7 +90,7 @@ <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Fetching_the_result"> <title>Fetching the result</title> <para> - Let's get nodes: + To fetch the nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -138,10 +100,10 @@ Node foundNode = it.nextNode(); }</programlisting> <para> - NodeIterator will return "/document3/jcr:content". + The <literal>NodeIterator</literal> will return <literal>/document3/jcr:content</literal>. </para> <para> - We can also get a table: + The results can also be formatted as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames(); Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-descendant-nodes.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-descendant-nodes.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/find-all-descendant-nodes.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -5,74 +5,33 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes"> <title>Finding All Descendant Nodes</title> - <para> - Find all nodes with the primary type 'nt:folder' that are descendants of the node "/folder1/folder2". - </para> + <formalpara> + <title>Task:</title> + <para> + Find all nodes with the primary type <literal>nt:folder</literal> that are descendants of the node <literal>/folder1/folder2</literal>. + </para> + </formalpara> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Repository_Structure"> <title>Repository Structure</title> <para> - The repository contains "nt:folder" nodes. The nodes are placed in a multilayer tree. + The repository contains <literal>nt:folder</literal> nodes. The nodes are placed in a multilayer tree. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - folder1 (nt:folder) - </para> - <itemizedlist> - <listitem> - <para> - folder2 (nt:folder) - </para> - <itemizedlist> - <listitem> - <para> - folder3 (nt:folder) // This node we want to find - </para> - <itemizedlist> - <listitem> - <para> - folder4 (nt:folder) // This node we want to find - </para> +<programlisting>root + └── folder1 (nt:folder) + └── folder2 (nt:folder) + ├── folder3 (nt:folder) // This node we want to find + │ └── folder4 (nt:folder) // This node we want to find + └── folder5 (nt:folder) // This node we want to find +</programlisting> - </listitem> - - </itemizedlist> - - </listitem> - <listitem> - <para> - folder5 (nt:folder) // This node we want to find - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Query_Execution"> <title>Query Execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -80,10 +39,11 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -91,13 +51,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Fetching_the_Result"> <title>Fetching the Result</title> <para> - Let's get nodes: + To fetch the nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -107,10 +69,10 @@ Node findedNode = it.nextNode(); }</programlisting> <para> - The NodeIterator will return "folder3", "folder4" and "folder5" nodes. + The <literal>NodeIterator</literal> will return "folder3", "folder4" and "folder5" nodes. </para> <para> - We can also get a table: + The results can also be output as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames(); Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -4,28 +4,29 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node"> - <title>Changing Priority of Node</title> - <para> - In this example, we will set different boost values for predefined nodes, and will check effect by selecting those nodes and order them by jcr:score. - </para> - <para> - The default boost value is 1.0. Higher boost values (a reasonable range is 1.0 - 5.0) will yield a higher score value and appear as more relevant. - </para> - <note> - <para> - See 4.2.2 Index Boost Value <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> - </para> + <title>Changing Priority of Node</title> + <formalpara> + <title></title> + <para> + Set different boost values for predefined nodes, and check the effect of this change by selecting those nodes and order them by <literal>jcr:score</literal>. + </para> + </formalpara> - </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Indexing_configuration"> - <title>Indexing configuration</title> - <para> - In next configuration, we will set boost values for nt:unstructured nodes 'text' property. - </para> - <para> - indexing-config.xml: - </para> - + <para> + The default boost value is <literal>1.0</literal>. Higher boost values (a reasonable range is between <literal>1.0</literal> and <literal>5.0</literal>) will yield a higher score value and appear as more relevant. + </para> + <para> + Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more information. + </para> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Indexing_configuration"> + <title>Indexing configuration</title> + <para> + In this configuration the boost values for <literal>nt:unstructured</literal> nodes <emphasis>text</emphasis> property will be increased. + </para> + +<example> + <title>indexing-config.xml:</title> <programlisting language="XML" role="XML"> @@ -49,53 +50,29 @@  <property boost="3.0">text</property> </index-rule></programlisting> +</example> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Repository_structure"> - <title>Repository structure:</title> - <para> - Repository contains many nodes with primary type nt:unstructured. Each node contains 'text' property and 'rule' property with different values. - </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - node1(nt:unstructured) rule='boost1' text='The quick brown fox jump...' - </para> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Repository_structure"> + <title>Repository structure:</title> + <para> + The repository contains many nodes with primary type <literal>nt:unstructured</literal>. Each node contains <emphasis>text</emphasis> property and <emphasis>rule</emphasis> property with different values. + </para> +<programlisting>root + ├── node1(nt:unstructured) rule='boost1' text='The quick brown fox jump...' + ├── node2(nt:unstructured) rule='boost2' text='The quick brown fox jump...' + └── node3(nt:unstructured) rule='boost3' text='The quick brown fox jump...' +</programlisting> - </listitem> - <listitem> - <para> - node2(nt:unstructured) rule='boost2' text='The quick brown fox jump...' - </para> - - </listitem> - <listitem> - <para> - node3(nt:unstructured) rule='boost3' text='The quick brown fox jump...' - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Query_execution"> - <title>Query execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Query_execution"> + <title>Query execution</title> + + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -103,10 +80,12 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -114,28 +93,46 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Fetching_result"> - <title>Fetching result</title> - <para> - Let's get nodes: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Fetching_result"> + <title>Fetching result</title> + <para> + To fetch the nodes: + </para> + <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); if(it.hasNext()) { Node findedNode = it.nextNode(); }</programlisting> - <para> - NodeIterator will return nodes in next order "node3", "node2", "node1". - </para> + <para> + The <literal>NodeIterator</literal> will return the nodes in this order: + </para> + <orderedlist> + <listitem> + <para> + node3 + </para> + </listitem> + <listitem> + <para> + node2 + </para> + </listitem> + <listitem> + <para> + node1 + </para> + </listitem> + </orderedlist> + </section> + - </section> - - </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/offset-and-limit.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/offset-and-limit.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/offset-and-limit.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -4,95 +4,63 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit"> - <title>SetOffset and SetLimit</title> - <para> - Select all nodes with primary type 'nt:unstructured' and returns only 3 nodes starting with the second node in the list. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Common_info"> - <title>Common info</title> - <para> - QueryImpl class has two methods: one to indicate how many results shall be returned at most, and another to fix the starting position. - </para> - <itemizedlist> - <listitem> - <para> - setOffset(long offset) - Sets the start offset of the result set. - </para> + <title><literal>SetOffset</literal> and <literal>SetLimit</literal></title> + <formalpara> + <title>Task:</title> + <para> + Select all nodes with primary type <literal>nt:unstructured</literal> and return only three nodes starting with the second node in the list. + </para> + </formalpara> - </listitem> - <listitem> - <para> - setLimit(long position) - Sets the maximum size of the result set. - </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Common_info"> + <title>Common information</title> + <para> + <literal>QueryImpl</literal> class has two methods; one to indicate how many results shall be returned at most, and another to fix the starting position. + </para> + <variablelist> + <title></title> + <varlistentry> + <term>setOffset(long offset)</term> + <listitem> + <para> + Sets the start offset of the result set. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>setLimit(long position)</term> + <listitem> + <para> + Sets the maximum size of the result set. + </para> + </listitem> + </varlistentry> + </variablelist> - </listitem> + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Repository_structure"> + <title>Repository structure</title> + <para> + The repository contains <literal>mix:title</literal> nodes, where <literal>jcr:title</literal> has different values. + </para> +<programlisting>root + ├── node1 (nt:unstructured) + ├── node2 (nt:unstructured) + ├── node3 (nt:unstructured) + ├── node4 (nt:unstructured) + ├── node5 (nt:unstructured) + └── node6 (nt:unstructured) +</programlisting> - </itemizedlist> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Repository_structure"> - <title>Repository structure</title> - <para> - Repository contains mix:title nodes, where jcr:title has different values. - </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - node1 (nt:unstructured) - </para> - - </listitem> - <listitem> - <para> - node2 (nt:unstructured) - </para> - - </listitem> - <listitem> - <para> - node3 (nt:unstructured) - </para> - - </listitem> - <listitem> - <para> - node4 (nt:unstructured) - </para> - - </listitem> - <listitem> - <para> - node5 (nt:unstructured) - </para> - - </listitem> - <listitem> - <para> - node6 (nt:unstructured) - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Query_execution"> - <title>Query execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Query_execution"> + <title>Query execution</title> + + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -104,30 +72,32 @@ query.setLimit(3); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Fetching_result"> - <title>Fetching result</title> - <para> - Let's get nodes: - </para> - + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Fetching_result"> + <title>Fetching result</title> + <para> + To fetch the matching nodes: + </para> + <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); if(it.hasNext()) { Node findedNode = it.nextNode(); }</programlisting> - <para> - In usual case (without using setOffset and setLimit methods), Node iterator returns all nodes (node1...node6). But in our case NodeIterator will return "node2","node3" and "node4". - </para> - <para> - \[node1 <emphasis role="bold">node2</emphasis> <emphasis role="bold">node3</emphasis> <emphasis role="bold">node4</emphasis> node5 node6\] - </para> + <para> + In usual cases (without using <literal>setOffset</literal> and <literal>setLimit</literal> methods), the <literal>NodeIterator</literal> returns all nodes (<emphasis>node1</emphasis> to <emphasis>node6</emphasis>). However in this case <literal>NodeIterator</literal> will return; <emphasis>node2</emphasis>, <emphasis>node3</emphasis> and <emphasis>node4</emphasis>. + </para> + <para> + \[node1 <emphasis role="bold">node2</emphasis> <emphasis role="bold">node3</emphasis> <emphasis role="bold">node4</emphasis> node5 node6\] + </para> - </section> - + </section> + </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/or-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/or-constraint.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/or-constraint.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -5,56 +5,31 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint"> <title>OR Constraint</title> - <para> - Find all documents whose title is 'Cinderella' or whose description is 'novel'. - </para> - <para> - How does it sound in jcr terms? - Find all nodes with a mixin type 'mix:title' whose property 'jcr:title' equals "Cinderella" or whose "jcr:description" property value is "novel". - </para> + <formalpara> + <title>Task:</title> + <para> + Find all documents whose title is <emphasis>Cinderella</emphasis> OR whose description is <emphasis>novel</emphasis>. In JCR terms this would be; find all nodes with a mixin type <literal>mix:title</literal> whose property <parameter>jcr:title</parameter> equals <emphasis>Cinderella</emphasis> or whose <parameter>jcr:description</parameter> property value is <emphasis>novel</emphasis>. + </para> + </formalpara> + <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains mix:title nodes, where jcr:title and jcr:description have different values. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (mix:title) jcr:title="War and peace" jcr:description="novel" - </para> - - </listitem> - <listitem> - <para> - document2 (mix:title) jcr:title="Cinderella" jcr:description="fairytale" - </para> - - </listitem> - <listitem> - <para> - document3 (mix:title) jcr:title="Puss in Boots" jcr:description="fairytale" - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - +<programlisting>root + ├── document1 (mix:title) jcr:title="War and peace" jcr:description="novel" + ├── document2 (mix:title) jcr:title="Cinderella" jcr:description="fairytale" + └── document3 (mix:title) jcr:title="Puss in Boots" jcr:description="fairytale" +</programlisting> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Query_Execution"> <title>Query Execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -62,10 +37,11 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -73,13 +49,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> - Let's get nodes: + To fetch matching nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -89,10 +67,10 @@ Node findedNode = it.nextNode(); }</programlisting> <para> - NodeIterator will return "document1" and "document2". + The <literal>NodeIterator</literal> will return <emphasis>document1</emphasis> and <emphasis>document2</emphasis>. </para> <para> - We can also get a table: + The output can also be formatted as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames(); Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/order-by-score.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/order-by-score.xml 2011-11-15 03:32:03 UTC (rev 8066) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/searching/order-by-score.xml 2011-11-15 03:36:33 UTC (rev 8067) @@ -5,13 +5,19 @@ ]> <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score"> <title>Ordering by Score</title> + <formalpara> + <title>Task:</title> + <para> + Select all nodes with the mixin type <literal>mix:title</literal> containing any word from the set {<emphasis>brown</emphasis>, <emphasis>fox</emphasis>, <emphasis>jumps</emphasis>}. Then, sort the results by their score in ascending node. This way nodes that are a closer match to the query statement are in the last positions in the result list. + </para> + </formalpara> <para> - Select all nodes with the mixin type 'mix:title' containing any word from the set {'brown','fox','jumps'}. Then, sort result by the score in ascending node. This way nodes that match better the query statement are ordered at the last positions in the result list. + </para> <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Info"> <title>Info</title> <para> - SQL and XPath queries support both score constructions jcr:score and jcr:score() + SQL and XPath queries both support score constructions <literal>jcr:score</literal> and <literal>jcr:score()</literal>. </para> <programlisting>SELECT * FROM nt:base ORDER BY jcr:score [ASC|DESC] @@ -20,12 +26,12 @@ //element(*,nt:base) order by jcr:score() [descending] //element(*,nt:base) order by @jcr:score [descending]</programlisting> <para> - Do not use "ascending" combined with jcr:score in XPath. The following XPath statement may throw an exception: + Do not use <parameter>ascending</parameter> combined with <literal>jcr:score</literal> in XPath. The following XPath statement may throw an exception: </para> <programlisting>... order by jcr:score() ascending</programlisting> <para> - Do not set any ordering specifier - ascending is default: + If you do not set any ordering specifier the default is ascending: </para> <programlisting>... order by jcr:score()</programlisting> @@ -37,45 +43,18 @@ <para> The repository contains mix:title nodes, where the jcr:description has different values. </para> - <itemizedlist> - <listitem> - <para> - root - </para> - <itemizedlist> - <listitem> - <para> - document1 (mix:title) jcr:description="The quick brown fox jumps over the lazy dog." - </para> - - </listitem> - <listitem> - <para> - document2 (mix:title) jcr:description="The brown fox lives in the forest." - </para> - - </listitem> - <listitem> - <para> - document3 (mix:title) jcr:description="The fox is a nice animal." - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - +<programlisting>root + ├── document1 (mix:title) jcr:description="The quick brown fox jumps over the lazy dog." + ├── document2 (mix:title) jcr:description="The brown fox lives in the forest." + └── document3 (mix:title) jcr:description="The fox is a nice animal." +</programlisting> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Query_Execution"> <title>Query Execution</title> - <para> - <emphasis role="bold">SQL</emphasis> - </para> - + <formalpara> + <title>SQL</title> + <para> <programlisting language="Java" role="Java">// make SQL query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -83,10 +62,12 @@ Query query = queryManager.createQuery(sqlStatement, Query.SQL); // execute query and fetch result QueryResult result = query.execute();</programlisting> - <para> - <emphasis role="bold">XPath</emphasis> - </para> - + </para> + </formalpara> + + <formalpara> + <title>XPath</title> + <para> <programlisting language="Java" role="Java">// make XPath query QueryManager queryManager = workspace.getQueryManager(); // create query @@ -94,13 +75,15 @@ Query query = queryManager.createQuery(xpathStatement, Query.XPATH); // execute query and fetch result QueryResult result = query.execute();</programlisting> + </para> + </formalpara> </section> <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Fetching_the_Result"> <title>Fetching the Result</title> <para> - Let's get nodes + To fetch the nodes: </para> <programlisting language="Java" role="Java">NodeIterator it = result.getNodes(); @@ -110,10 +93,10 @@ Node findedNode = it.nextNode(); }</programlisting> <para> - NodeIterator will return nodes in the following order: "document3", "document2", "document1". + The <literal>NodeIterator</literal> will return nodes in the following order: <emphasis>document3</emphasis>, <emphasis>document2</emphasis>, <emphasis>document1</emphasis>. </para> <para> - We can also get a table: + The results can also be formatted as a table: </para> <programlisting language="Java" role="Java">String[] columnNames = result.getColumnNames();

13 years, 2 months

1
0
0 / 0

gatein SVN: r8066 - portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/workspace.

by do-not-reply＠jboss.org

Author: ndkhoiits Date: 2011-11-14 22:32:03 -0500 (Mon, 14 Nov 2011) New Revision: 8066 Modified: portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/workspace/UIMainActionListener.java Log: GTNPORTAL-2272 Portlet windows doesn't appear in some cases Modified: portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/workspace/UIMainActionListener.java =================================================================== --- portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/workspace/UIMainActionListener.java 2011-11-15 03:27:23 UTC (rev 8065) +++ portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/workspace/UIMainActionListener.java 2011-11-15 03:32:03 UTC (rev 8066) @@ -60,7 +60,7 @@ static public class PageCreationWizardActionListener extends EventListener<UIWorkingWorkspace> { public void execute(Event<UIWorkingWorkspace> event) throws Exception - { + { UIPortalApplication uiApp = Util.getUIPortalApplication(); UIPortal uiPortal = Util.getUIPortal(); UIWorkingWorkspace uiWorkingWS = uiApp.getChildById(UIPortalApplication.UI_WORKING_WS_ID); @@ -69,7 +69,6 @@ if (currNav == null) { uiApp.addMessage(new ApplicationMessage("UIPortalManagement.msg.navigation.deleted", null)); - event.getRequestContext().addUIComponentToUpdateByAjax(uiWorkingWS); return; } @@ -107,10 +106,10 @@ uiToolPanel.setWorkingComponent(UIPageCreationWizard.class, null); UIPageCreationWizard uiWizard = (UIPageCreationWizard)uiToolPanel.getUIComponent(); uiWizard.configure(resolvedNode); - + UIWizardPageSetInfo uiPageSetInfo = uiWizard.getChild(UIWizardPageSetInfo.class); uiPageSetInfo.setShowPublicationDate(false); - event.getRequestContext().addUIComponentToUpdateByAjax(uiWorkingWS); + event.getRequestContext().addUIComponentToUpdateByAjax(uiWorkingWS); } private UserNode resolveNode(UserNode selectedNode, UserNodeFilterConfig filterConfig) throws Exception

13 years, 2 months

1
0
0 / 0

gatein SVN: r8065 - portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form.

by do-not-reply＠jboss.org

Author: ndkhoiits Date: 2011-11-14 22:27:23 -0500 (Mon, 14 Nov 2011) New Revision: 8065 Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormInputWithActions.java Log: GTNPORTAL-2271 UIFormInputWithAction render children regardless of is rendered or not Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormInputWithActions.java =================================================================== --- portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormInputWithActions.java 2011-11-15 02:23:37 UTC (rev 8064) +++ portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormInputWithActions.java 2011-11-15 03:27:23 UTC (rev 8065) @@ -78,70 +78,73 @@ for (UIComponent inputEntry : getChildren()) { - String label; - try + if (inputEntry.isRendered()) { - label = uiForm.getLabel(res, inputEntry.getId()); - if (inputEntry instanceof UIFormInputBase) - ((UIFormInputBase)inputEntry).setLabel(label); - } - catch (MissingResourceException ex) - { - label = inputEntry.getId(); - log.error("\n " + uiForm.getId() + ".label." + inputEntry.getId() + " not found value"); - } - w.write("<tr>"); - w.write("<td class=\"FieldLabel\">"); - w.write(label); - w.write("</td>"); - w.write("<td class=\"FieldComponent\">"); - renderUIComponent(inputEntry); - List<ActionData> actions = actionField.get(inputEntry.getName()); - if (actions != null) - { - for (ActionData action : actions) + String label; + try { - String actionLabel; - try + label = uiForm.getLabel(res, inputEntry.getId()); + if (inputEntry instanceof UIFormInputBase) + ((UIFormInputBase)inputEntry).setLabel(label); + } + catch (MissingResourceException ex) + { + label = inputEntry.getId(); + log.error("\n " + uiForm.getId() + ".label." + inputEntry.getId() + " not found value"); + } + w.write("<tr>"); + w.write("<td class=\"FieldLabel\">"); + w.write(label); + w.write("</td>"); + w.write("<td class=\"FieldComponent\">"); + renderUIComponent(inputEntry); + List<ActionData> actions = actionField.get(inputEntry.getName()); + if (actions != null) + { + for (ActionData action : actions) { - actionLabel = uiForm.getLabel(res, "action." + action.getActionName()); + String actionLabel; + try + { + actionLabel = uiForm.getLabel(res, "action." + action.getActionName()); + } + catch (MissingResourceException ex) + { + actionLabel = action.getActionName(); + log.debug("Key: '" + uiForm.getId() + ".label.action." + action.getActionName() + + "' not found"); + } + String actionLink; + if (action.getActionParameter() != null) + { + actionLink = + getParent().event(action.getActionListener(), action.getActionParameter()); + } + else + { + actionLink = getParent().event(action.getActionListener()); + } + + if (action.getActionType() == ActionData.TYPE_ICON) + { + w.write("<img title=\"" + actionLabel + "\" onclick=\"" + actionLink + "\" " + + "src=\"/eXoResources/skin/DefaultSkin/background/Blank.gif\" class=\"" + + action.getCssIconClass() + "\" alt=\"\"/>"); + if (action.isShowLabel) + w.write(actionLabel); + } + else if (action.getActionType() == ActionData.TYPE_LINK) + { + w.write("<a title=\"" + actionLabel + "\" href=\"" + actionLink + "\">" + actionLabel + "</a>"); + } + w.write(" "); + if (action.isBreakLine()) + w.write("<br/>"); } - catch (MissingResourceException ex) - { - actionLabel = action.getActionName(); - log.debug("Key: '" + uiForm.getId() + ".label.action." + action.getActionName() - + "' not found"); - } - String actionLink; - if (action.getActionParameter() != null) - { - actionLink = - getParent().event(action.getActionListener(), action.getActionParameter()); - } - else - { - actionLink = getParent().event(action.getActionListener()); - } - - if (action.getActionType() == ActionData.TYPE_ICON) - { - w.write("<img title=\"" + actionLabel + "\" onclick=\"" + actionLink + "\" " - + "src=\"/eXoResources/skin/DefaultSkin/background/Blank.gif\" class=\"" - + action.getCssIconClass() + "\" alt=\"\"/>"); - if (action.isShowLabel) - w.write(actionLabel); - } - else if (action.getActionType() == ActionData.TYPE_LINK) - { - w.write("<a title=\"" + actionLabel + "\" href=\"" + actionLink + "\">" + actionLabel + "</a>"); - } - w.write(" "); - if (action.isBreakLine()) - w.write("<br/>"); } + w.write("</td>"); + w.write("</tr>"); } - w.write("</td>"); - w.write("</tr>"); } w.write("</table>"); w.write("</div>");

13 years, 2 months

1
0
0 / 0

gatein SVN: r8064 - epp/docs/branches/5.2/Developer_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-14 21:23:37 -0500 (Mon, 14 Nov 2011) New Revision: 8064 Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml Log: Edits in prep for beta release Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2011-11-15 01:32:28 UTC (rev 8063) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2011-11-15 02:23:37 UTC (rev 8064) @@ -4,131 +4,132 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Developer_Guide-Architectural_choices"> - <title>Architectural choices</title> - <para> - Depending on environment and goals, decisions has to be made regarding the components that will make up the final website. Some elements may already be in place (such as an identity server) and some elements may still be free to choose. This section aims at helping taking the right decisions. - </para> - <section id="sect-Developer_Guide-Architectural_choices-Identity_server"> - <title>Identity server</title> - <para> - EPP 5.2 comes with a component named PicketLink IDM, which is made to adapt to store and retrieve users and groups from various identity servers. We can separate the different options into three: - </para> - <orderedlist> - <listitem> - <para> - <emphasis role="strong">Database</emphasis> : users, groups and their relationships are stored in a RDBMS database. Tables names and column names can be changed, but the overall relationship between tables remains the same. This solution is particularly adapted to a new identity server that will handle thousands of users. - </para> + <title>Architectural choices</title> + <para> + Depending on environment and goals, decisions has to be made regarding the components that will make up the final website. Some elements may already be in place (such as an identity server) and some elements may still be free to choose. This section aims at helping taking the right decisions. + </para> + <section id="sect-Developer_Guide-Architectural_choices-Identity_server"> + <title>Identity server</title> + <para> + JBoss Enterprise Portal Platform &VY; comes with a component named PicketLink IDM, which is made to adapt to store and retrieve users and groups from various identity servers. We can separate the different options into three: + </para> + <orderedlist> + <listitem> + <para> + <emphasis role="strong">Database</emphasis> : users, groups and their relationships are stored in a RDBMS database. Tables names and column names can be changed, but the overall relationship between tables remains the same. This solution is particularly adapted to a new identity server that will handle thousands of users. + </para> - </listitem> - <listitem> - <para> - <emphasis role="strong">LDAP</emphasis> : users, groups and their relationships are stored in an LDAP (or ActiveDirectory) server, the directory structure can be adapted by configuration to the most common scenarios. This solution is particularly adapted to infrastructure that are already using an LDAP server, for infrastructure that will share the server identity among multiple service (and the website being one of them) or for very large set of users (millions). When using LDAP with large number of users, it is recommended to use LDAP tools to do the provisioning of users. - </para> + </listitem> + <listitem> + <para> + <emphasis role="strong">LDAP</emphasis> : users, groups and their relationships are stored in an LDAP (or ActiveDirectory) server, the directory structure can be adapted by configuration to the most common scenarios. This solution is particularly adapted to infrastructure that are already using an LDAP server, for infrastructure that will share the server identity among multiple service (and the website being one of them) or for very large set of users (millions). When using LDAP with large number of users, it is recommended to use LDAP tools to do the provisioning of users. + </para> - </listitem> - <listitem> - <para> - <emphasis role="strong">Custom</emphasis> : when retrieving users, groups and their relationship cannot be done by configuration, it is possible to implement the Picketlink IDM SPI to implement the methods in charge of retrieving and storing user information. - </para> + </listitem> + <listitem> + <para> + <emphasis role="strong">Custom</emphasis> : when retrieving users, groups and their relationship cannot be done by configuration, it is possible to implement the Picketlink IDM SPI to implement the methods in charge of retrieving and storing user information. + </para> - </listitem> + </listitem> - </orderedlist> - <para> - Picketlink IDM also supports mix environments, this is very useful when an LDAP infrastructure is provided but in a read-only mode. Since the website may need to store additional information about users (such as his preferred language or skin), it can combine LDAP + Database, to retrieve users from LDAP but store additional properties in a database. During the calls to the identity API, the information from both sources will be transparently merged. For more information about PicketLink IDM, please check the EPP 5.2 reference guide and the PicketLink IDM documentation. - </para> + </orderedlist> + <para> + Picketlink IDM also supports mix environments, this is very useful when an LDAP infrastructure is provided but in a read-only mode. Since the website may need to store additional information about users (such as his preferred language or skin), it can combine LDAP + Database, to retrieve users from LDAP but store additional properties in a database. During the calls to the identity API, the information from both sources will be transparently merged. For more information about PicketLink IDM, please check the JBoss Enterprise Portal Platform &VY; reference guide and the PicketLink IDM documentation. + </para> - </section> - - <section id="sect-Developer_Guide-Architectural_choices-Storage"> - <title>Storage</title> - <para> - The portal framework stores page compositions, portlet preferences, gadget code in a database through a Java Content Repository (JCR) API. A set of database servers and JDBC connectors are part of our quality assurance cycles and the certified environments are mentioned <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . - </para> - <para> - It is important to choose one of the combination or check with a Red Hat contact for specific environments that would differ from this list. - </para> - <para> - The database schema will be automatically created during the very first startup of the website and then it is required that the database users has sufficient rights to create tables. This privilege can be revoked after the initial startup, also the database content can be exported and imported in a new server. This makes the installation of the product very easy in most cases. - </para> - <para> - We do not provide additional recommendation to choose a database server over another as long as it is part of our certified environment. - </para> - <para> - As said earlier content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of database, metadata about the files would still be stored into the database. Note that if the website is running on a cluster the filesystem will need to be accessible from all nodes and a NFS solution needs to be setup. For more details see the notion of "value storage" in the reference guide. - </para> + </section> + + <section id="sect-Developer_Guide-Architectural_choices-Storage"> + <title>Storage</title> + <para> + The portal framework stores page compositions, portlet preferences, gadget code in a database through a Java Content Repository (JCR) API. A set of database servers and JDBC connectors are part of our quality assurance cycles and the certified environments are mentioned <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . + </para> + <para> + It is important to choose one of the combination or check with a Red Hat contact for specific environments that would differ from this list. + </para> + <para> + The database schema will be automatically created during the very first startup of the website and then it is required that the database users has sufficient rights to create tables. This privilege can be revoked after the initial startup, also the database content can be exported and imported in a new server. This makes the installation of the product very easy in most cases. + </para> + <para> + We do not provide additional recommendation to choose a database server over another as long as it is part of our certified environment. + </para> + <para> + As said earlier content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of database, metadata about the files would still be stored into the database. Note that if the website is running on a cluster the filesystem will need to be accessible from all nodes and a NFS solution needs to be setup. For more details see the notion of "value storage" in the reference guide. + </para> - </section> - - <section id="sect-Developer_Guide-Architectural_choices-Cluster"> - <title>Cluster</title> - <para> - Clustering for failover or load-balancing requirements requires to spend more time configuring it for your environment, we made it easy to handle common situations though. There is a cost associated to clustering (EPP 5.2 has some optimization when running on a single node) but the product is designed to linearly scale up so that same performance is added every time a new node is added. All critical parts are kept in sync among nodes and the less critical ones left aside to achieve better performance. It will be equally critical that applications developed for the final websites pay the same attention when it comes to replicate data across a cluster of nodes. - </para> - <para> - The number of nodes will vary a lot depending on the applications developed and used on the final website. We recommend to do early performance analysis with tools such as JMeter, Grinder etc to measure the impact of heavy loads. - </para> - <para> - It is usually recommended to run a cluster to achieve high availability. - </para> + </section> + + <section id="sect-Developer_Guide-Architectural_choices-Cluster"> + <title>Cluster</title> + <para> + Clustering for failover or load-balancing requirements requires to spend more time configuring it for your environment, we made it easy to handle common situations though. There is a cost associated to clustering (JBoss Enterprise Portal Platform &VY; has some optimization when running on a single node) but the product is designed to linearly scale up so that same performance is added every time a new node is added. All critical parts are kept in sync among nodes and the less critical ones left aside to achieve better performance. It will be equally critical that applications developed for the final websites pay the same attention when it comes to replicate data across a cluster of nodes. + </para> + <para> + The number of nodes will vary a lot depending on the applications developed and used on the final website. We recommend to do early performance analysis with tools such as JMeter, Grinder etc to measure the impact of heavy loads. + </para> + <para> + It is usually recommended to run a cluster to achieve high availability. + </para> - </section> - - <section id="sect-Developer_Guide-Architectural_choices-SSO"> - <title>SSO</title> - <para> - If the website is part of a more global infrastructure with various components (the website being one of several), it may be in the benefit of users to put a Single-Sign-On solution in place among them. Various SSO solutions are supported by EPP 5.2 as seen <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . In some cases it can be better to have the token manager service on a specific server. - </para> - <para> - Summary - </para> - <para> - By now you should know what infrastructure you will need: - </para> - <para> - - A database - </para> - <para> - - Optionally LDAP, depending on your choice - </para> - <para> - - Optionally NFS, depending on the configuration (mandatory on a cluster with default settings: TODO: More QA on a setup without NFS) - </para> - <para> - - Optionally an SSO token service - </para> - <para> - - Optionally, a cluster of nodes - </para> - <para> - Here is an example of the simplest setup: - </para> - <figure id="figu-Developer_Guide-SSO-Simple_Infrastructure"> - <title>Simple Infrastructure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372876/simpleinfra.png" width="444" /> - </imageobject> + </section> + + <section id="sect-Developer_Guide-Architectural_choices-SSO"> + <title>SSO</title> + <para> + If the website is part of a more global infrastructure with various components (the website being one of several), it may be in the benefit of users to put a Single-Sign-On solution in place among them. Various SSO solutions are supported by JBoss Enterprise Portal Platform &VY; as seen <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . In some cases it can be better to have the token manager service on a specific server. + </para> + <para> + Summary + </para> + <para> + By now you should know what infrastructure you will need: + </para> + <para> + - A database + </para> + <para> + - Optionally LDAP, depending on your choice + </para> + <para> + - Optionally NFS, depending on the configuration (mandatory on a cluster with default settings: +  + </para> + <para> + - Optionally an SSO token service + </para> + <para> + - Optionally, a cluster of nodes + </para> + <para> + Here is an example of the simplest setup: + </para> + <figure id="figu-Developer_Guide-SSO-Simple_Infrastructure"> + <title>Simple Infrastructure</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372876/simpleinfra.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> - <para> - Here is an example of a more complex setup: - </para> - <figure id="figu-Developer_Guide-SSO-Complex_Infrastructure"> - <title>Complex Infrastructure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372876/complexinfra.png" width="444" /> - </imageobject> + </figure> + <para> + Here is an example of a more complex setup: + </para> + <figure id="figu-Developer_Guide-SSO-Complex_Infrastructure"> + <title>Complex Infrastructure</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372876/complexinfra.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> + </figure> - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml 2011-11-15 01:32:28 UTC (rev 8063) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml 2011-11-15 02:23:37 UTC (rev 8064) @@ -4,174 +4,174 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Developer_Guide-Design_choices"> - <title>Design choices</title> - <para> - Now that the main components of the architecture has been decided, choices must be made on the overall design. - </para> - <section id="sect-Developer_Guide-Design_choices-Dashboards"> - <title>Dashboards</title> - <para> - User dashboards may be very costly in a website, as each user will have the opportunity to design his own personal website, it comes with the cost of storing all that information. Efforts have been made (and are still made) to reduce this cost, but there will always be an overhead. - </para> - <para> - This overhead might be hard to estimate as this will depend a lot on how the users will navigate the website, maybe only a minority will use this functionality, or maybe the website is only made of dashboards. In any case the impact of making this feature available must be measured by: - </para> - <itemizedlist> - <listitem> - <para> - estimating the number of dashboards and pages that will be created - </para> + <title>Design choices</title> + <para> + Now that the main components of the architecture has been decided, choices must be made on the overall design. + </para> + <section id="sect-Developer_Guide-Design_choices-Dashboards"> + <title>Dashboards</title> + <para> + User dashboards may be very costly in a website, as each user will have the opportunity to design his own personal website, it comes with the cost of storing all that information. Efforts have been made (and are still made) to reduce this cost, but there will always be an overhead. + </para> + <para> + This overhead might be hard to estimate as this will depend a lot on how the users will navigate the website, maybe only a minority will use this functionality, or maybe the website is only made of dashboards. In any case the impact of making this feature available must be measured by: + </para> + <itemizedlist> + <listitem> + <para> + Estimating the number of dashboards and pages that will be created + </para> - </listitem> - <listitem> - <para> - observing the impact on the database (through JCR) in terms of size - </para> + </listitem> + <listitem> + <para> + Observing the impact on the database (through JCR) in terms of size + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Developer_Guide-Design_choices-JCR_index_replication_for_cluster_setup"> - <title>JCR index replication for cluster setup</title> - <para> - The JCR implementation uses Apache Lucene for indexing the data. The indexes are used to search for content (It can be page nodes or WCM content for instance). Lucene isn't cluster-ready but on a cluster, each node will need to be able to search for content and will need to have access to the lucene indexes. When is comes to searching, there is always a tradeoff. Everyone would want to achieve all of the following: - </para> - <itemizedlist> - <listitem> - <para> - Fast to search - </para> + </section> + + <section id="sect-Developer_Guide-Design_choices-JCR_index_replication_for_cluster_setup"> + <title>JCR index replication for cluster setup</title> + <para> + The JCR implementation uses Apache Lucene for indexing the data. The indexes are used to search for content (it can be page nodes or WCM content for instance). Lucene is not cluster-ready but on a cluster, each node will need to be able to search for content and will need to have access to the lucene indexes. All search implementations would want to achieve all of the following: + </para> + <itemizedlist> + <listitem> + <para> + Fast to search + </para> - </listitem> - <listitem> - <para> - Fast to index - </para> + </listitem> + <listitem> + <para> + Fast to index + </para> - </listitem> - <listitem> - <para> - Same search result on each node at the same time - </para> + </listitem> + <listitem> + <para> + Same search result on each node at the same time + </para> - </listitem> - <listitem> - <para> - No need to rebuild the index ever (No inconsistency) - </para> + </listitem> + <listitem> + <para> + No need to rebuild the index ever (No inconsistency) + </para> - </listitem> - <listitem> - <para> - No impact on overall performance - </para> + </listitem> + <listitem> + <para> + No impact on overall performance + </para> - </listitem> - <listitem> - <para> - Easy to setup (no infrastructure change) - </para> + </listitem> + <listitem> + <para> + Easy to setup (no infrastructure change) + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - But there are choices to be made. The JCR implementation used by EPP (eXo JCR) makes it possible to configure the storage and retrieval of indexes according to architect's choice on where it is acceptable to lose-up some constraints. For configuration details please refer to the EPP Reference Guide. - </para> - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Standalone_index"> - <title>Standalone index</title> - <para> - This is only for a non-cluster environment, this is obviously the easiest setup, with a combination of in-memory and file based indexes. There is no replication involved so any entry can be found by a search as soon as they are created. - <figure id="figu-Developer_Guide-Standalone_index-Standalone_Index"> - <title>Standalone Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-standalone-index.png" /> - </imageobject> + </itemizedlist> + <para> + The JCR implementation used by JBoss Enterprise Portal Platform (eXo JCR) makes it possible to configure the storage and retrieval of indexes according to architect's choice on where it is acceptable to lose-up some constraints. For configuration details please refer to the JBoss Enterprise Portal Platform Reference Guide. + </para> + <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Standalone_index"> + <title>Standalone index</title> + <para> + This is only for a non-cluster environment, this is obviously the easiest setup, with a combination of in-memory and file based indexes. There is no replication involved so any entry can be found by a search as soon as they are created. + <figure id="figu-Developer_Guide-Standalone_index-Standalone_Index"> + <title>Standalone Index</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372952/diagram-standalone-index.png" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> + </figure> - </para> + </para> - </section> - - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Local_index"> - <title>Local index</title> - <para> - This environment is easy to setup, each node keeps a local copy of the full indexes so that when a search is requested on a node, there is no network communication requested. The downside is that when a node indexes an item, it requires to replicate that index on each and every node. If a node is unavailable at that time, it may miss an index update request and then the different nodes may be inconsistent. Also when a node is added it has to recreate it's own full index. An alternative to this setup is to ask a node to retrieve the info from a coordinator on each search, it makes the startup of the new node faster but impacts its performance during the runtime. This setup is new to EPP 5.2. - </para> - <para> - <figure id="figu-Developer_Guide-Local_index-Local_Index"> - <title>Local Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-local-index.png" width="444" /> - </imageobject> + </section> + + <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Local_index"> + <title>Local index</title> + <para> + This environment is easy to setup, each node keeps a local copy of the full indexes so that when a search is requested on a node, there is no network communication requested. The downside is that when a node indexes an item, it requires to replicate that index on each and every node. If a node is unavailable at that time, it may miss an index update request and then the different nodes may be inconsistent. Also when a node is added it has to recreate its own full index. An alternative to this setup is to ask a node to retrieve the information from a coordinator on each search, it makes the startup of the new node faster but impacts its performance during the runtime. This setup is new to JBoss Enterprise Portal Platform &VY;. + </para> + <para> + <figure id="figu-Developer_Guide-Local_index-Local_Index"> + <title>Local Index</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372952/diagram-local-index.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> + </figure> - </para> + </para> - </section> - - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Shared_index"> - <title>Shared index</title> - <para> - In this setup there is a unique index created and shared among all nodes. It requires to configure the infrastructure so that a network file system is installed where all nodes can read content. Advantages: - </para> - <itemizedlist> - <listitem> - <para> - Consistency, all the nodes see the same data - </para> + </section> + + <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Shared_index"> + <title>Shared index</title> + <para> + In this setup there is a unique index created and shared among all nodes. It requires to configure the infrastructure so that a network file system is installed where all nodes can read content. Advantages: + </para> + <itemizedlist> + <listitem> + <para> + Consistency, all the nodes see the same data + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - Drawback: - </para> - <itemizedlist> - <listitem> - <para> - Requires a highly available NFS setup (NFS 4 is recommended) - </para> + </itemizedlist> + <para> + Drawback: + </para> + <itemizedlist> + <listitem> + <para> + Requires a highly available NFS setup (NFS 4 is recommended) + </para> - </listitem> - <listitem> - <para> - More network communication - </para> + </listitem> + <listitem> + <para> + More network communication + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - <figure id="figu-Developer_Guide-Shared_index-Shared_Index"> - <title>Shared Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-shared-index.png" width="444" /> - </imageobject> + </itemizedlist> + <para> + <figure id="figu-Developer_Guide-Shared_index-Shared_Index"> + <title>Shared Index</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372952/diagram-shared-index.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> + </figure> - </para> + </para> - </section> - + </section> + - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2011-11-15 01:32:28 UTC (rev 8063) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2011-11-15 02:23:37 UTC (rev 8064) @@ -4,112 +4,97 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Developer_Guide-Portal_Development"> - <title>Portal Development</title> - <section id="sect-Developer_Guide-Portal_Development-Portal_containers"> - <title>Portal containers</title> - <para> - In a single instance (or cluster) of EPP, multiple portals can be running and share resources with other portals with two level of granularities: - </para> - <itemizedlist> - <listitem> - <para> - Portal Containers: A portal container can host multiple sites, and an EPP instance can host multiple portal containers - </para> + <title>Portal Development</title> + <section id="sect-Developer_Guide-Portal_Development-Portal_containers"> + <title>Portal containers</title> + <para> + In a single instance (or cluster) of JBoss Enterprise Portal Platform, multiple portals can be running and share resources with other portals with two level of granularities: + </para> + <itemizedlist> + <listitem> + <para> + Portal Containers: A portal container can host multiple sites, and an JBoss Enterprise Portal Platform instance can host multiple portal containers + </para> - </listitem> - <listitem> - <para> - Site: A site can have a unique identity, with its own skin applied, set of pages... - </para> + </listitem> + <listitem> + <para> + Site: A site can have a unique identity, with its own skin applied, set of pages... + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - The biggest granularity is what is called "Portal Containers", a Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL Mapping according to the following scheme: <ulink url="http://localhost:8080/" /> <portalcontainer>/<site> - </para> - <para> - When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at <ulink url="http://localhost:8080/portal" /> on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installation, note that multiple websites can run in a single portal container and share some services. - </para> - <para> - By providing an extension you can benefit from the portal provided by EPP and be able to customize the parts you want. The benefits over directly modifying the shipped files is that it will make the updates much easier (By just replacing the archives provided by EPP). - <figure id="figu-Developer_Guide-Portal_containers-Portal_Extension_Structure"> - <title>Portal Extension Structure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372962/portalextensionstructure.png" width="444" /> - </imageobject> + </itemizedlist> + <para> + The biggest granularity is what is called "Portal Containers", a Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL Mapping according to the following scheme: <ulink url="http://localhost:8080/" /> <portalcontainer>/<site> + </para> + <para> + When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at <ulink url="http://localhost:8080/portal" /> on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installation, note that multiple websites can run in a single portal container and share some services. + </para> + <para> + By providing an extension you can benefit from the portal provided by JBoss Enterprise Portal Platform and be able to customize the parts you want. The benefits over directly modifying the shipped files is that it will make the updates much easier (By just replacing the archives provided by JBoss Enterprise Portal Platform). + <figure id="figu-Developer_Guide-Portal_containers-Portal_Extension_Structure"> + <title>Portal Extension Structure</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372962/portalextensionstructure.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> + </figure> - </para> - <section id="sect-Developer_Guide-Portal_containers-Portal_extension"> - <title>Portal extension</title> - <para> - A portal extension is packaged as an Enterprise ARchive (EAR), a configuration file allows to define which services are required and by ordering those, it is possible to modify some elements. It can be a configuration setting, a translation, a visual template, a page to add... - </para> - <para> - Portal extensions can shadow existing services, a portal will usually be composed of various extensions, each of them usually add services. - <figure id="figu-Developer_Guide-Portal_extension-Portal_Extensions"> - <title>Portal Extensions</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372962/portalExtensions.png" width="444" /> - </imageobject> + </para> + <section id="sect-Developer_Guide-Portal_containers-Portal_extension"> + <title>Portal extension</title> + <para> + A portal extension is packaged as an Enterprise ARchive (EAR), a configuration file allows to define which services are required and by ordering those, it is possible to modify some elements. It can be a configuration setting, a translation, a visual template, a page to add... + </para> + <para> + Portal extensions can shadow existing services, a portal will usually be composed of various extensions, each of them usually add services. + <figure id="figu-Developer_Guide-Portal_extension-Portal_Extensions"> + <title>Portal Extensions</title> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/7372962/portalExtensions.png" width="444" /> + </imageobject> - </mediaobject> + </mediaobject> - </figure> - In a portal extension, elements are shadowed by using the same directory location, so if one wants to rewrite the groovy template of the HomePagePortlet which is located in: gatein.ear/02portal.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl it would be located in an extension such as myExtension/myWar.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl. The ordering will be defined by the portal extension configuration. - </para> + </figure> + In a portal extension, elements are shadowed by using the same directory location, so if one wants to rewrite the groovy template of the HomePagePortlet which is located in: gatein.ear/02portal.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl it would be located in an extension such as myExtension/myWar.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl. The ordering will be defined by the portal extension configuration. + </para> - </section> - + </section> + - </section> - - <section id="sect-Developer_Guide-Portal_Development-Visual_identity"> - <title>Visual identity</title> - <para> - A portal visual identity will be made of the HTML produced by the result of the portal aggregation (the components that makes a page like columns, rows combined with the content produced by the portlets) and associated CSS files. - </para> - <para> - EPP allows to deploy multiple skins which consists of CSS files, it makes it possible to apply styling on the page compositions and components of a page (Portlets). Different skins can be applied to the different websites, also if made available to the users, they can choose their preferred skin. - </para> - <section id="sect-Developer_Guide-Visual_identity-Customizing_the_login_page"> - <title>Customizing the login page</title> - <para> - When accessing a page that requires privileges, a login page is showing up, that page can be customized by using an extension. To do so it would be enough to copy the file located at: - </para> - <example id="exam-Developer_Guide-Customizing_the_login_page-login.jsp"> - <title><filename>login.jsp</filename></title> - -<programlisting>gatein.ear/02portal.war/login/jsp/login.jsp</programlisting> + </section> + + <section id="sect-Developer_Guide-Portal_Development-Visual_identity"> + <title>Visual identity</title> + <para> + A portal visual identity will be made of the HTML produced by the result of the portal aggregation (the components that makes a page like columns, rows combined with the content produced by the portlets) and associated CSS files. + </para> + <para> + JBoss Enterprise Portal Platform allows to deploy multiple skins which consists of CSS files, it makes it possible to apply styling on the page compositions and components of a page (Portlets). Different skins can be applied to the different websites, also if made available to the users, they can choose their preferred skin. + </para> + <section id="sect-Developer_Guide-Visual_identity-Customizing_the_login_page"> + <title>Customizing the login page</title> + <para> + When accessing a page that requires privileges, a login page is showing up, that page can be customized by using an extension. To do so it would be enough to copy the file located at <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> and include it in the portal extension such as <filename>myExtension.ear/myWar.war/login/jsp/login.jsp</filename>. + </para> + <para> + All the logic must be carefully kept in the login page so that the portal will keep working as it should. + </para> + <para> + To modify the modal window which pops up when the user decides to sign-in, the extension would have a modified copy of <filename>gatein.ear/02portal.war/groovy/portal/webui/UILoginForm.gtmpl</filename> + </para> + + </section> + - </example> - <para> - and include it in the portal extension such as myExtension.ear/myWar.war/login/jsp/login.jsp - </para> - <para> - All the logic must be carefully kept in the login page so that the portal will keep working as it should. - </para> - <para> - To modify the modal window which pops up when the user decides to sign-in, the extension would have a modified copy of: - </para> - <example id="exam-Developer_Guide-Customizing_the_login_page-UILoginForm.gtmpl"> - <title><filename>UILoginForm.gtmpl</filename></title> - -<programlisting>gatein.ear/02portal.war/groovy/portal/webui/UILoginForm.gtmpl</programlisting> + </section> + - </example> - - </section> - - - </section> - - </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2011-11-15 01:32:28 UTC (rev 8063) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2011-11-15 02:23:37 UTC (rev 8064) @@ -4,45 +4,45 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Developer_Guide-Application_development"> - <title>Application development</title> - <section id="sect-Developer_Guide-Application_development-Gadget_Development"> - <title>Gadget Development</title> - <section id="sect-Developer_Guide-Gadget_Development-Introduction"> - <title>Introduction</title> - <para> - In the context of EPP, gadgets are those as defined by the Google OpenSocial specifications. Since EPP 5.2, the portal framework includes Apache Shindig 2.0 which is made to support the version 0.9 and 1.0 of OpenSocial. - </para> - <para> - Within a portal it is possible to embed any OpenSocial gadget on a page or within the user dashboards, gadgets can be added to the application registry, or links can be added within the mini-composer (see the User Guide). - </para> + <title>Application development</title> + <section id="sect-Developer_Guide-Application_development-Gadget_Development"> + <title>Gadget Development</title> + <section id="sect-Developer_Guide-Gadget_Development-Introduction"> + <title>Introduction</title> + <para> + In the context of JBoss Enterprise Portal Platform, gadgets are those as defined by the Google OpenSocial specifications. Since JBoss Enterprise Portal Platform 5.2, the portal framework includes Apache Shindig 2.0 which is made to support the version 0.9 and 1.0 of OpenSocial. + </para> + <para> + Within a portal it is possible to embed any OpenSocial gadget on a page or within the user dashboards, gadgets can be added to the application registry, or links can be added within the mini-composer (see the User Guide). + </para> - </section> - - <section id="sect-Developer_Guide-Gadget_Development-Developing_Gadgets"> - <title>Developing Gadgets</title> - <para> - OpenSocial gadgets are made of standard HTML and javascript. The container offers an API for which the documentation is available <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Gadget.xml">here</ulink> . - </para> - <para> - Note that unlike portlets, a gadget has very little knowledge of its context (the portal) and its integration within the portal may be more limited (in terms of visual integration for instance). - </para> - <para> - Google Web Toolkit (GWT) applications can also be used as gadgets, it makes it easy to write user-friendly applications. - </para> + </section> + + <section id="sect-Developer_Guide-Gadget_Development-Developing_Gadgets"> + <title>Developing Gadgets</title> + <para> + OpenSocial gadgets are made of standard HTML and javascript. The container offers an API for which the documentation is available <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Gadget.xml">here</ulink> . + </para> + <para> + Note that unlike portlets, a gadget has very little knowledge of its context (the portal) and its integration within the portal may be more limited (in terms of visual integration for instance). + </para> + <para> + Google Web Toolkit (GWT) applications can also be used as gadgets, it makes it easy to write user-friendly applications. + </para> - </section> - + </section> + - </section> - - <section id="sect-Developer_Guide-Application_development-Portlet_Development"> - <title>Portlet Development</title> - <para> - ToDo. - </para> + </section> + + <section id="sect-Developer_Guide-Application_development-Portlet_Development"> + <title>Portlet Development</title> + <para> + ToDo. + </para> - </section> - + </section> + </chapter>

13 years, 2 months

1
0
0 / 0

gatein SVN: r8063 - epp/docs/branches/5.2/Admin_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-14 20:32:28 -0500 (Mon, 14 Nov 2011) New Revision: 8063 Added: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml Log: Incorporating latest chenges from nscavelli Added: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml 2011-11-15 01:32:28 UTC (rev 8063) @@ -0,0 +1,284 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-8094332_GateInManagement-Introduction"> + + <title>Introduction</title> + <para>The management component of the portal allows portal resources to be managed over commons interfaces like REST, CLI, and Portlets/Gadgets. This guide will discuss these interfaces as well as general portal management concepts and terms. It will then discuss specific management extensions included in the portal.</para> + <section id="sid-8094332_GateInManagement-Terms"> + + <title>Terms</title> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para>Term</para> + </entry> + <entry> + <para> + Description + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Management Extension</para> + </entry> + <entry> + <para>An extension to the management system which defines a managed component.</para> + </entry> + </row> + <row> + <entry> + <para> + Managed Component + + </para> + </entry> + <entry> + <para>A managed component, which has been registered via an extension, serves as the root managed resource for a component.</para> + </entry> + </row> + <row> + <entry> + <para> + Managed Resource + + </para> + </entry> + <entry> + <para> + A managed resource is a uniquely identified self describing 'resource' which can have operations and sub-resources registered to it. + + </para> + </entry> + </row> + <row> + <entry> + <para> + Sub-resource + + </para> + </entry> + <entry> + <para> + A managed resource whose parent is also a managed resource. + + </para> + </entry> + </row> + <row> + <entry> + <para> + Address + + </para> + </entry> + <entry> + <para> + A management address is just the path of the managed resource with syntax similar to a file on a file system, ie: /foo/bar + + </para> + </entry> + </row> + <row> + <entry> + <para> + Operation + + </para> + </entry> + <entry> + <para> + An action that can be performed on a managed resource. + + </para> + </entry> + </row> + <row> + <entry> + <para> + Attributes + + </para> + </entry> + <entry> + <para> + Custom input parameters available to operations. + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </section> + <section id="sid-8094332_GateInManagement-Goals"> + + <title>Goals</title> + <para>The management component provides a foundation for managing portal side components. By doing so it allows management extensions to register resources and operations over a set of API's, which in turn allows us to expose these over common interfaces like REST and CLI. In other words, management extensions don't have to worry about the interfaces in which they will be managed over. This allows us to add additional interfaces without needing to change anything. Also by providing a set of API's to obtain managed resources, interfaces are built in a consistent manner. So managing the same component in one interface should be very similar if you were to manage it in another.</para> + </section> + <section id="sid-8094332_GateInManagement-Operations"> + + <title>Operations</title> + <para> + The following operations are operations that have been identified by the management component to be common to most management extensions. The + <code>read-resource</code> + operation is really the only global operation supported in the core framework, all other operations need to be implemented by the extensions, since these would be specific to each extension. + </para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para>Operation Name</para> + </entry> + <entry> + <para> + Description + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + read-resource + + </para> + </entry> + <entry> + <para> + The read-resource operation is responsible for reading the managed resource; describing itself and listing any operations and/or sub-resources it may contain. + + This is the primary operation to obtain information about a managed component and it's managed resources. + </para> + </entry> + </row> + <row> + <entry> + <para> + add-resource + + </para> + </entry> + <entry> + <para>The add-resource operation is responsible for adding/creating additional managed resources.</para> + </entry> + </row> + <row> + <entry> + <para> + remove-resource + + </para> + </entry> + <entry> + <para>The remove-resource operation is responsible for removing/deleting an existing managed resource.</para> + </entry> + </row> + <row> + <entry> + <para>update-resource</para> + </entry> + <entry> + <para>The update-resource operation is responsible for updating an existing managed resources state.</para> + </entry> + </row> + <row> + <entry> + <para> + read-config-as-xml + + </para> + </entry> + <entry> + <para>The read-config-as-xml operation is responsible for representing the current managed resource as xml configuration.</para> + </entry> + </row> + <row> + <entry> + <para> + export-resource + + </para> + </entry> + <entry> + <para> + The export-resource operation is responsible for exporting a managed resource in a format that is acceptable and used in an import. The export-resource is special in the + + sense that there's built-in functionality to recursively traverse managed resources until it finds one that supports an export-resource operation. In other words you can + + register an export-resource operation on a sub-resource and it will be executed even by calling export-resource on any of it's ancestors. + + </para> + </entry> + </row> + <row> + <entry> + <para> + import-resource + + </para> + </entry> + <entry> + <para> + The import-resource operation is responsible for importing managed resources previously exported through an export-resource operation. + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </section> + <section id="sid-8094332_GateInManagement-ContentType"> + + <title>Content Type</title> + <para>Content type defines the format of management requests/responses. The three content types supported at the moment are json, xml, and zip. Since read-config-as-xml (xml), export-resource (zip), and import-resource (zip) are content type specific operations, the response must be in that format. Other then that it's up to the extension on which content type is supported for each operation.</para> + </section> + <section id="sid-8094332_GateInManagement-PathTemplates"> + + <title>Path Templates</title> + <para> + Path templates are something that management extensions use to define dynamic content when registering resources. These path template variables are used during an export-resource to filter these managed resources. By specifying the + <code>filter</code> + attribute of an export-resource operation, managed resources can be explicitly included or excluded during export. + </para> + <para>The filter attribute has the following value syntax:</para> + <example> + <title>Filter Syntax</title> + <programlisting>[path-var]:(!)?[name],...[name];...[path-var]:(!)?[name],...[name]</programlisting> + </example> + <para>where path-var is the path template variable name, name is the name of a managed-resource, and the '!' char, which is optional, is to exclude that resource rather then include it. Below are some examples that use the path template variable 'foo':</para> + <example> + <title>Only include managed resource 'bar'</title> + <programlisting>foo:bar</programlisting> + </example> + <example> + <title>Include managed resource 'bar' and 'foo-bar'</title> + <programlisting>foo:bar,foo-bar</programlisting> + </example> + <example> + <title>Exclude managed resource 'bar'</title> + <programlisting>foo:!bar</programlisting> + </example> + <example> + <title>Exclude managed resource 'bar' and 'foo-bar'</title> + <programlisting>foo:!bar,foo-bar</programlisting> + </example> + <example> + <title>Multiple path template variables (foo and baz) separated by the ';' char</title> + <programlisting>foo:bar,foo-bar;baz:blah</programlisting> + </example> + <note> + <title>Note</title> + <para>For more information on the usage of path templates specific to a management extension, see the management extensions section below.</para> + </note> + </section> + </chapter> Added: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml 2011-11-15 01:32:28 UTC (rev 8063) @@ -0,0 +1,502 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-8094332_GateInManagement-REST"> + + <title>REST</title> + <para>The management REST component is responsible for mapping restful requests to management requests. It does this by locating the managed resource by mapping the request URL to a management address and then invoking an operation on that managed resource. It defines an entry point for RESTful clients, and exposes the registered managed resources and operations over REST.</para> + <section id="sid-8094332_GateInManagement-EntryPoint"> + + <title>Entry Point</title> + <para>To gain access to management resources and operations over REST a RESTful client must know the entry point URL, which is defined as follows:</para> + <example> + <title>URL Syntax</title> + <programlisting>http(s)://&lt;host&gt;:&lt;port&gt;/&lt;rest-context-name&gt;/private/managed-components</programlisting> + </example> + <para>Where the rest-context-name is the portal container's rest context name. So for the default portal, the rest context name is 'rest', and for a portal running on localhost and port 8080 the URL would be</para> + <example> + <title>URL Example</title> + <programlisting>http://localhost:8080/rest/private/managed-components/</programlisting> + </example> + <note> + <title>Note</title> + <para>The REST URL is protected, and the authenticated user must belong to the 'administrators' group of the portal.</para> + </note> + </section> + <section id="sid-8094332_GateInManagement-ResourceURLs"> + + <title>Resource URLs</title> + <para>REST resource URLs are mapped to management addresses, and since every managed resource has a unique management address, every managed resource can be represented by a unique REST URL. The URL for identifying managed resources is as follows:</para> + <example> + <title>URL Syntax</title> + <programlisting>http://&lt;host&gt;:&lt;port&gt;/&lt;rest-context-name&gt;/private/managed-components/&lt;component-name&gt;/&lt;managed-resource-name&gt;/&lt;sub-resource-name&gt;/.../&lt;sub-resource-name&gt;</programlisting> + </example> + <para>The URL below uniquely identifies a managed resource named 'foo-bar', which is a sub-resource of 'bar', and 'bar' being a managed resource of the managed component 'foo'.</para> + <example> + <title>URL Example</title> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar/foo-bar</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-Operationsx"> + + <title>Operations</title> + <para>To map a RESTful request to an operation the REST component must somehow map the HTTP request to an operation name. It can achieve this by looking at three things (in order of precedence):</para> + <itemizedlist> + <listitem> + <para>HTTP URL Parameters</para> + </listitem> + <listitem> + <para>URL Extension</para> + </listitem> + <listitem> + <para>The HTTP method of the request.</para> + </listitem> + </itemizedlist> + <section id="sid-8094332_GateInManagement-HTTPMethod"> + + <title>HTTP Method</title> + <para>The following table shows which HTTP methods map to operation names.</para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para> + HTTP Method + + </para> + </entry> + <entry> + <para> + Management Operation + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + GET + + </para> + </entry> + <entry> + <para> + read-resource + + </para> + </entry> + </row> + <row> + <entry> + <para> + PUT + + </para> + </entry> + <entry> + <para> + update-resource + + </para> + </entry> + </row> + <row> + <entry> + <para> + POST + + </para> + </entry> + <entry> + <para> + add-resource + + </para> + </entry> + </row> + <row> + <entry> + <para> + DELETE + + </para> + </entry> + <entry> + <para> + remove-resource + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>This means that the same URL can invoke four different operations just by changing the HTTP method of the REST request.</para> + </section> + <section id="sid-8094332_GateInManagement-RequestParameter"> + + <title>Request Parameter</title> + <para> + Since the management system supports more then just four operations, operations can also be explicitly defined by including HTTP parameters as part of the REST request. For example by adding the query parameter + <emphasis role="strong">op</emphasis> + to the request URL, clients can define what operation to invoke. + </para> + <example> + <title>Custom operation defined in request parameter</title> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?op=some-cus...</programlisting> + </example> + <para>It's best practice to use the HTTP method to dictate the operation name when it can. However nothing stops a client explicitly setting operation names as request parameters.</para> + <note> + <title>Note</title> + <para>The following URL's are equivalent for a GET request:</para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar"/> + </para> + </listitem> + <listitem> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar?op=read-res..."/> + </para> + </listitem> + </itemizedlist> + </note> + </section> + <section id="sid-8094332_GateInManagement-URLExtension"> + + <title>URL Extension</title> + <para>Sometimes it's nice to represent REST resources as files, so two URL extensions have been added to support two common operations: read-config-as-xml and export-resource. By adding the following URL extensions at the end of the URL, you can invoke these two operations.</para> + <informaltable> + <tgroup cols="3"> + <thead> + <row> + <entry> + <para> + URL Extension + + </para> + </entry> + <entry> + <para> + Management Operation + + </para> + </entry> + <entry> + <para> + Example URL + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + .xml + + </para> + </entry> + <entry> + <para> + read-config-as-xml + + </para> + </entry> + <entry> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar.xml"/> + </para> + </entry> + </row> + <row> + <entry> + <para> + .zip + + </para> + </entry> + <entry> + <para> + export-resource + + </para> + </entry> + <entry> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar.zip"/> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>This is just a convenient way to specify the operation name as a file extension instead of specifying it as a request parameter.</para> + <note> + <title>Note</title> + <para>The following URL's are equivalent:</para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar.xml"/> + </para> + </listitem> + <listitem> + <para> + <ulink url="http://localhost:8080/rest/private/managed-components/foo/bar?op=read-con..."/> + </para> + </listitem> + </itemizedlist> + </note> + </section> + </section> + <section id="sid-8094332_GateInManagement-Attributes"> + + <title>Attributes</title> + <para>Management attributes (which are part of a management request) are mapped by including all request parameters of the HTTP request as attributes. So if an operation supports certain attributes, query parameters can be added to the request URL to be used as attributes of the management request.</para> + <example> + <title>Attributes first-name and last-name as request parameters</title> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?first-name=...</programlisting> + </example> + <section id="sid-8094332_GateInManagement-MultivalueAttributes"> + + <title>Multi-value Attributes</title> + <para>Management attributes can be multi-valued (meaning more then one value associated with an attribute). This is easy as HTTP query parameters can be multi-valued as well.</para> + <example> + <title>Multi-valued attribute colors as request parameters</title> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?colors=red&...</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-ContentNegotiation"> + + <title>Content Negotiation</title> + <para> + The management framework defines Content Type to indicate the format of management requests and responses. Clients can dictate the content type of the management request by specifying the + <code>Accept</code> + and + <code>Content-Type</code> + headers of the HTTP request. The + <code>Accept</code> + header indicates the format of the response and the + <code>Content-Type</code> + header specifies the format of the request. Below is a list of request headers that map to the Content Type of the management system. + </para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para> + Header + + </para> + </entry> + <entry> + <para> + Content Type + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + application/json + + </para> + </entry> + <entry> + <para> + JSON + + </para> + </entry> + </row> + <row> + <entry> + <para> + application/xml + + </para> + </entry> + <entry> + <para> + XML + + </para> + </entry> + </row> + <row> + <entry> + <para> + application/zip + + </para> + </entry> + <entry> + <para> + ZIP + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <note> + <title>Note</title> + <para>JSON is the default content type.</para> + </note> + <section id="sid-8094332_GateInManagement-BrowserContentNegotiation"> + + <title>Browser Content Negotiation</title> + <para> + To make it easy to control the content type of management requests through the browser, the rest component supports the + <code>format</code> + HTTP parameter to dictate the format of the response. This is because most browsers already send an 'Accept' header. + </para> + <example> + <title>Specifying the response should be returned as xml</title> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?format=xml</programlisting> + </example> + <para> + Below is the list of + <code>format</code> + HTTP parameters which map to Content Types. + </para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para> + Format parameter + + </para> + </entry> + <entry> + <para> + Content Type + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + format=json (default) + + </para> + </entry> + <entry> + <para> + JSON + + </para> + </entry> + </row> + <row> + <entry> + <para> + format=xml + + </para> + </entry> + <entry> + <para> + XML + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <important> + <title>Important</title> + <para>Content negotiation is ignored for content type specific operations such as 'read-config-as-xml' and 'export-resource' since these cannot return different formats.</para> + </important> + </section> + <section id="sid-8094332_GateInManagement-readresource"> + + <title>resource</title> + <para> + Since the + <code>read-resource</code> + operation is a built in operation provided by the management component, as opposed to extensions, below documents the format of the response. + </para> + <example> + <title>HTTP Request</title> + <programlisting>GET /managed-components + +or + +GET /managed-components?op=read-resource</programlisting> + </example> + <example> + <title>Response as JSON</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/json + +{ + "description": "Available operations and children (sub-resources).", + "children": [ + { + "name": "foo", + "description": "Some description", + "link": { + "rel": "child", + "href": "http://localhost:8080/rest/private/managed-components/foo" + } + } + ], + "operations": [ + { + "operation-name": "read-resource", + "operation-description": "Lists information about a managed resource, including available operations and children (sub-resources).", + "link": { + "rel": "self", + "href": "http://localhost:8080/rest/private/managed-components" + "type": "application/json" + "method": "get" + } + } + ] +}</programlisting> + </example> + <example> + <title>Response as XML</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt; +&lt;resource&gt; + &lt;description&gt;Available operations and children (sub-resources).&lt;/description&gt; + &lt;children&gt; + &lt;child&gt; + &lt;name&gt;foo&lt;/name&gt; + &lt;description&gt;Some description&lt;/description&gt; + &lt;link href="http://localhost:8080/rest/private/managed-components/foo" rel="child"/&gt; + &lt;/child&gt; + &lt;/children&gt; + &lt;operations&gt; + &lt;operation&gt; + &lt;operation-name&gt;read-resource&lt;/operation-name&gt; + &lt;operation-description&gt;Lists information about a managed resource, including available operations and children (sub-resources).&lt;/operation-description&gt; + &lt;link href="http://localhost:8080/rest/private/managed-components" rel="self" type="application/xml" method="get"/&gt; + &lt;/operation&gt; + &lt;/operations&gt; +&lt;/resource&gt;</programlisting> + </example> + </section> + </section> + </chapter> Added: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-3-Command_Line_Interface.xml 2011-11-15 01:32:28 UTC (rev 8063) @@ -0,0 +1,352 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-8094332_GateInManagement-CommandLineInterface"> + + <title>Command Line Interface</title> + <para>The command line interface (CLI) component provides an interactive shell using CRaSH to map commands to management requests. It connects over SSH, using the CRaSH SSH plugin.</para> + <note> + <title>Note</title> + <para> + For more information on CRaSH please visit + <ulink url="http://code.google.com/p/crsh/"/> + . + </para> + </note> + <section id="sid-8094332_GateInManagement-DeployingtheCLI"> + + <title>Deploying the CLI</title> + <para> + To deploy the CLI you must first build the gatein-management project. The source is available on + <ulink url="http://github.com/gatein/gatein-management">github</ulink> + . Once built you can then deploy the web application to a GateIn instance like below: + </para> + <example> + <title>Copy CLI artifact as an exploded war to application server</title> + <programlisting>cp -r cli/target/gatein-management-cli $JBOSS_HOME/server/default/deploy/gatein-management-cli.war</programlisting> + </example> + <important> + <title>Important</title> + <para>The CLI web application must be deployed as an exploded war</para> + </important> + </section> + <section id="sid-8094332_GateInManagement-RunningtheCLI"> + + <title>Running the CLI</title> + <para>After deploying the CLI web application you can connect to the CLI over SSH as follows</para> + <example> + <title>SSH Syntax</title> + <programlisting>ssh -p &lt;port&gt; &lt;user&gt;@&lt;host&gt;</programlisting> + </example> + <example> + <title>SSH Example</title> + <programlisting>ssh -p 2000 root@localhost</programlisting> + </example> + <para> + You can change the default port that SSH listens on by changing the property crash.ssh.port in the + <code>WEB-INF/crash/crash.properties</code> + file. + </para> + <example> + <title>crash.properties</title> + <programlisting># VFS configuration +crash.vfs.refresh_period=1 + +# SSH configuration +crash.ssh.port=2000</programlisting> + </example> + <important> + <title>Important</title> + <para>Make sure the configured port is open and not blocked by firewall settings.</para> + </important> + </section> + <section id="sid-8094332_GateInManagement-Commands"> + + <title>Commands</title> + <para> + The CLI component comes with a number of management commands that will execute operations on managed resources in the portal. For a listing of all commands available type in + <emphasis role="strong">help</emphasis> + in the shell. You can also add the help option + <emphasis role="strong">-h</emphasis> + or + <emphasis role="strong">--help</emphasis> + for each command for further information. Also the + <emphasis role="strong">man</emphasis> + command can be executed for even more detailed information about the command. + </para> + <section id="sid-8094332_GateInManagement-mgmt"> + + <title>mgmt</title> + <para> + The mgmt command allows a user to connect and disconnect from the management system. It also provides an + <code>exec</code> + command which allows more custom control over executing operations with the management system. + </para> + <example> + <title>mgmt help</title> + <programlisting>% mgmt -h +usage: mgmt[-h | --help] COMMAND [ARGS] + +The most commonly used mgmt commands are: + exec Manually executes a management operation + connect login to gatein management + disconnect disconnect from management system + +% mgmt connect -h +usage: mgmt [-h | --help] connect [-u | --username] [-p | --password] [-c | --container] + + [-h | --help] command usage + [-u | --username] the user name + [-p | --password] the user passowrd + [-c | --container] portal container name (default is portal) + +%</programlisting> + </example> + <para> + The + <code>mgmt connect</code> + command allows the user to connect to the management system, optionally specifying a portal container (default is 'portal'). Since management commands are administrative operations, the user must authenticate again in order to validate authorization to the portal container. + </para> + <example> + <title>Connecting to default portal container</title> + <programlisting>% mgmt connect +Password: +Successfully connected to gatein management system: [user=root, container='portal', host='127.0.0.1'] + +[ /]%</programlisting> + </example> + <example> + <title>Connecting to portal container 'sample-portal' as user john</title> + <programlisting>% mgmt connect -u john -c sample-portal +Password: +Successfully connected to gatein management system: [user=john, container='sample-portal', host='127.0.0.1'] + +[ /]%</programlisting> + </example> + <para> + The + <code>mgmt exec</code> + command allows complete control over what to send to the management system. + </para> + <example> + <title>mgmt exec help</title> + <programlisting>[ /]% mgmt exec -h +usage: mgmt [-h | --help] exec [-c | --contentType] [-f | --file] [-a | --attribute] [-o | --operation] path + + [-h | --help] command usage + [-c | --contentType] content type of an operation + [-f | --file] File name + [-a | --attribute] Specifies an attribute. + [-o | --operation] Operation name + path + +[ /]%</programlisting> + </example> + <example> + <title>Executing operation read-config-as-xml on managed component foo</title> + <programlisting>[ /]% mgmt exec --operation read-config-as-xml --contentType xml /foo +&lt;?xml version='1.0' encoding='UTF-8'?&gt; +&lt;data&gt;...&lt;/data&gt; + +[ /]%</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-cat"> + + <title>cat</title> + <para> + The + <code>cat</code> + command executes the + <code>read-config-as-xml</code> + operation on a managed resource and outputs the xml data to the shell. Obviously the managed resource must support the + <code>read-config-as-xml</code> + operation. + </para> + <example> + <title>cat help</title> + <programlisting>[ /]% cat -h +usage: cat [-h | --help] path + + [-h | --help] command usage + path + +[ /]% cat /foo +&lt;?xml version='1.0' encoding='UTF-8'?&gt; +&lt;data&gt;...&lt;/data&gt; + +[ /]%</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-cd"> + + <title>cd</title> + <para>The cd command changes the current path of the CLI.</para> + <example> + <title>cd help</title> + <programlisting>[ /]% cd -h +usage: cd [-h | --help] path + + [-h | --help] command usage + path + +[ /]%</programlisting> + </example> + <example> + <title>Change path to /foo/bar</title> + <programlisting>[ /]% cd /foo/bar + +[bar]%</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-ls"> + + <title>ls</title> + <para> + The + <code>ls</code> + command executes the + <code>read-resource</code> + operation on the current (or specified by the path) managed resource. + </para> + <example> + <title>ls help</title> + <programlisting>[ /]% ls -h +usage: ls [-h | --help] path + + [-h | --help] command usage + path + +[ /]% ls +foo +bar + +[ /]% ls /foo +baz + +[ /]%</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-pwd"> + + <title>pwd</title> + <para> + The + <code>pwd</code> + command prints out the current resource path of the CLI. + </para> + <example> + <title>pwd help</title> + <programlisting>[ /]% pwd -h +usage: pwd [-h | --help] + + [-h | --help] command usage + +[ /]% pwd +/ +[ /]% cd foo/baz + +[baz]% pwd +/foo/baz + +[baz]%</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-export"> + + <title>export</title> + <para> + The + <code>export</code> + operation executes the + <code>export-resource</code> + operation on a managed resource and writes the exported content to the file. + </para> + <important> + <title>Important</title> + <para>Since the CLI is connected to the portal server over SSH, the export command will write to the servers file system, not the client.</para> + </important> + <example> + <title>export help</title> + <programlisting>[ /]% export -h +usage: export [-h | --help] [-f | --file] [-r | --filter] path + + [-h | --help] command usage + [-f | --file] File name + [-r | --filter] Specifies the value of the filter to use during an export for example. + path + +[ /]%</programlisting> + </example> + <example> + <title>Export resource foo to /tmp directory</title> + <programlisting>[ /]% export --file /tmp foo +Export complete ! File location: /tmp/foo_2011-10-21_18-29-36.zip + +[ /%]</programlisting> + </example> + <note> + <title>Note</title> + <para>If you only specify a directory the export command will write a file with the name of the managed resource and a timestamp.</para> + </note> + <example> + <title>Export resource /foo to /tmp/export-example.zip file</title> + <programlisting>[ /]% export --file /tmp/export-example.zip foo +Export complete ! File location: /tmp/export-example.zip + +[ /%]</programlisting> + </example> + <example> + <title>Export resource filtering on path template variable bar</title> + <programlisting>[ /]% export --file /tmp/export-filter-example.zip --filter bar:baz,foo-bar foo +Export complete ! File location: /tmp/export-filter-example.zip + +[ /%]</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-import"> + + <title>import</title> + <para> + The + <code>import</code> + command executes the + <code>import-resource</code> + operation on a managed resource. + </para> + <example> + <title>import help</title> + <programlisting>[ /]% import -h +usage: importfile [-h | --help] [-f | --file] [-m | --importMode] path + + [-h | --help] command usage + [-f | --file] File name + [-m | --importMode] The import mode for an import operation + path + +[ /]%</programlisting> + </example> + <important> + <title>Important</title> + <para>Since the CLI is connected to the portal server over SSH, the import command must specify a file that exists on the server.</para> + </important> + <example> + <title>Import file /tmp/foo.zip to resource foo</title> + <programlisting>[ /]% import --file /tmp/foo.zip /foo +Successfully imported file /tmp/foo.zip + +[ /]%</programlisting> + </example> + <example> + <title>Import file /tmp/foo.zip to resource foo using importMode overwrite</title> + <programlisting>[ /]% import --file /tmp/foo.zip --importMode overwrite /foo +Successfully imported file /tmp/foo.zip + +[ /]%</programlisting> + </example> + <note> + <title>Note</title> + <para>You can autocomplete the import modes by typing --importMode and hitting tab.</para> + </note> + </section> + </section> + </chapter> Added: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml 2011-11-15 01:32:28 UTC (rev 8063) @@ -0,0 +1,558 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-8094332_GateInManagement-ManagementExtensions"> + + <title>Management Extensions</title> + <para>The following management extensions supported in the portal are:</para> + <itemizedlist> + <listitem> + <para>MOP Management Extension</para> + </listitem> + </itemizedlist> + <section id="sid-8094332_GateInManagement-MOPManagementExtension"> + + <title>MOP Management Extension</title> + <para>The MOP management extension registers the 'mop' managed component which is responsible for managing pages, navigation, and site layout. It primarily supports exporting and importing this data through the export-resource and import-resource operations. It also supports the read-config-as-xml operation to expose the portal meta data as xml.</para> + </section> + <section id="sid-8094332_GateInManagement-Operationsxx"> + + <title>Operations</title> + <section id="sid-8094332_GateInManagement-readconfigasxml"> + + <title>config-as-xml</title> + <para> + The + <code>read-config-as-xml</code> + operation can only be executed on the site layout, pages, and navigation managed resources. The xml format returned is that of which is defined in by the + <ulink url="http://www.gatein.org/xml/ns/">gatein-objects</ulink> + xsd. This means that these resources are exposed in the same format as what a portal extension would accept for importing data into the portal. + </para> + </section> + <section id="sid-8094332_GateInManagement-exportresource"> + + <title>export-resource</title> + <para> + The + <code>export-resource</code> + operation can be executed on any resource of the MOP extension (including the mop component itself). Since the management system recursively searches for all sub-resources that have export-resource defined (which they are defined at the site layout, page, and navigation level), exports can be very granular. + </para> + </section> + <section id="sid-8094332_GateInManagement-importresource"> + + <title>import-resource</title> + <para> + The + <code>import-resource</code> + operation can only be executed at the mop component (root managed resource of the mop extension). This is because the exported zip file contains the path information (like site type and site name). So executing an + <code>import-resource</code> + operation on a group site, when the zip contains data from a portal site, doesn't make sense. + </para> + <para> + The MOP + <code>import-resource</code> + operation defines the + <code>importMode</code> + attribute as follows during import. + </para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para> + Mode + + </para> + </entry> + <entry> + <para> + Description + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + conserve + + </para> + </entry> + <entry> + <para> + Import data only if no artifacts exist for that site. For example if one page exists for site 'classic', nothing will be imported. + + </para> + </entry> + </row> + <row> + <entry> + <para> + insert + + </para> + </entry> + <entry> + <para> + Import data when data does not exist, otherwise do nothing. + + </para> + </entry> + </row> + <row> + <entry> + <para> + merge + + </para> + </entry> + <entry> + <para> + Import when data does not exist, update data when it does exist. + + </para> + </entry> + </row> + <row> + <entry> + <para> + overwrite + + </para> + </entry> + <entry> + <para> + Delete all data for that artifact of the site, import new data. For example if the zip file only contains pages for site classic, then + + all pages for that site are deleted and imported. + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <note> + <title>Note</title> + <para>'merge' is the default importMode.</para> + </note> + </section> + </section> + <section id="sid-8094332_GateInManagement-PathTemplatesx"> + + <title>Path Templates</title> + <para>Below are the list of path template variables defined in the MOP management extension. These path template variables are used for filtering during export.</para> + <itemizedlist> + <listitem> + <para> + <code>site-type</code> + + These are the site types of the portal to include or exclude. Available values are: + <code>portal</code> + , + <code>group</code> + , and + <code>user</code> + . + </para> + </listitem> + <listitem> + <para> + <code>site-name</code> + + The sites to include or exclude. Examples could be + <code>classic</code> + and + <code>/platform/administrators</code> + . + </para> + </listitem> + <listitem> + <para> + <code>site-layout</code> + + The name of the site layout depending on the site type. Available values are: + <code>portal</code> + , + <code>group</code> + , + <code>user</code> + . + </para> + </listitem> + <listitem> + <para> + <code>page-name</code> + + The name of the page(s) to include or exclude. + </para> + </listitem> + <listitem> + <para> + <code>nav-uri</code> + + The URI of the navigation node to include or exclude. + </para> + </listitem> + </itemizedlist> + </section> + <section id="sid-8094332_GateInManagement-RESTAPI"> + + <title>REST API</title> + <note> + <title>Note</title> + <para>All URL's below are relative to the REST management entry point of the portal container.</para> + </note> + <note> + <title>Note</title> + <para> + For all read-config-as-xml refer + <ulink url="http://www.gatein.org/xml/ns/gatein_objects_1_2"/> + for the format of the XML. + </para> + </note> + <section id="sid-8094332_GateInManagement-MOPComponentResource"> + + <title>MOP Component Resource</title> + <para> + The mop managed component resource (root managed resource) is the only resource that accepts the + <code>import-resource</code> + operation. + </para> + <example> + <title>HTTP Request</title> + <programlisting>PUT /mop + +Headers: + Content-Type: application/zip</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-SiteLayoutResource"> + + <title>Site Layout Resource</title> + <para> + The site layout resource represents the site layout of the portal. It's the data defined in the + <emphasis role="strong">portal.xml</emphasis> + , + <emphasis role="strong">group.xml</emphasis> + , and + <emphasis role="strong">user.xml</emphasis> + files (depending on site type) used in portal extensions to configure data. + </para> + <example> + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/{site-layout}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlx"> + + <title>config-as-xml</title> + <para>Example of reading the site layout as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/portal.xml + +or + +GET /mop/portalsites/classic/portal?op=read-config-as-xml</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;portal-config&gt; + &lt;portal-name&gt;classic&lt;/portal-name&gt; + &lt;label&gt;Classic&lt;/label&gt; + &lt;description&gt;GateIn default portal&lt;/description&gt; + &lt;locale&gt;en&lt;/locale&gt; +... +&lt;/portal-config&gt;</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresourcex"> + + <title>export-resource</title> + <para>Example of exporting the site layout for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/portal.zip + +or + +GET /mop/portalsites/classic/portal?op=export-resource</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/zip + +[binary data]</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-PagesResource"> + + <title>Pages Resource</title> + <para>The pages resource represents the pages of the portal. It's the data defined in the pages.xml used in portal extensions to configure data.</para> + <example> + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/pages/{page-name}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlxx"> + + <title>config-as-xml</title> + <para>Example of reading all pages as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages.xml + +or + +GET /mop/portalsites/classic/pages?op=read-config-as-xml</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;page-set&gt; + &lt;page&gt; + &lt;name&gt;homepage&lt;/name&gt; + &lt;title&gt;Home Page&lt;/title&gt; + &lt;access-permissions&gt;Everyone&lt;/access-permissions&gt; + &lt;edit-permission&gt;*:/platform/administrators&lt;/edit-permission&gt; + &lt;show-max-window&gt;false&lt;/show-max-window&gt; + &lt;portlet-application&gt; +... +&lt;/page-set&gt;</programlisting> + </example> + <para>Example of reading the homepage as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages/homepage.xml + +or + +GET /mop/portalsites/classic/pages/homepage?op=read-config-as-xml</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;page-set&gt; + &lt;page&gt; + &lt;name&gt;homepage&lt;/name&gt; + &lt;title&gt;Home Page&lt;/title&gt; + &lt;access-permissions&gt;Everyone&lt;/access-permissions&gt; + &lt;edit-permission&gt;*:/platform/administrators&lt;/edit-permission&gt; + &lt;show-max-window&gt;false&lt;/show-max-window&gt; + &lt;portlet-application&gt; +... +&lt;/page-set&gt;</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresourcexx"> + + <title>export-resource</title> + <para>Example of exporting all pages of site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages.zip + +or + +GET /mop/portalsites/classic/pages?op=export-resource</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/zip + +[binary data]</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-NavigationResource"> + + <title>Navigation Resource</title> + <para>The navigation resource represents the navigation of the portal. It's the data defined in the navigation.xml used in portal extensions to configure data.</para> + <example> + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/navigation/{nav-uri}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlxxx"> + + <title>config-as-xml</title> + <para>Example of reading all navigation as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation.xml + +or + +GET /mop/portalsites/classic/navigation?op=read-config-as-xml</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;node-navigation&gt; + &lt;priority&gt;1&lt;/priority&gt; + &lt;page-nodes&gt; + &lt;node&gt; + &lt;name&gt;home&lt;/name&gt; + &lt;label xml:lang="en"&gt;Home&lt;/label&gt; + ... + &lt;visibility&gt;DISPLAYED&lt;/visibility&gt; + &lt;page-reference&gt;portal::classic::homepage&lt;/page-reference&gt; + &lt;/node&gt; + &lt;node&gt; + &lt;name&gt;sitemap&lt;/name&gt; +... +&lt;/node-navigation&gt;</programlisting> + </example> + <para>Example of reading the home node as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation/home.xml + +or + +GET /mop/portalsites/classic/navigation/home?op=read-config-as-xml</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/xml + +&lt;node-navigation&gt; + &lt;priority&gt;1&lt;/priority&gt; + &lt;page-nodes&gt; + &lt;parent-uri&gt;&lt;/parent-uri&gt; + &lt;node&gt; + &lt;name&gt;home&lt;/name&gt; + &lt;label xml:lang="en"&gt;Home&lt;/label&gt; + ... + &lt;visibility&gt;DISPLAYED&lt;/visibility&gt; + &lt;page-reference&gt;portal::classic::homepage&lt;/page-reference&gt; + &lt;/node&gt; + &lt;/page-nodes&gt; +&lt;/node-navigation&gt;</programlisting> + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresource_Example"> + + <title>export-resource Example</title> + <para>Example of exporting all navigation of site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation.zip + +or + +GET /mop/portalsites/classic/navigation?op=export-resource</programlisting> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK +Content-Type: application/zip + +[binary data]</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-ExportandFiltering-1"> + + <title>Export and Filtering</title> + <para> + Filtering is activated when the + <code>filter</code> + attribute is passed to an + <code>export-resource</code> + operation. The filter attribute is a multi-value attribute that is passed as request parameters of the HTTP request. + </para> + <note> + <title>Note</title> + <para>You can either include multiple filter parameters (?filter=foo:bar&filter=baz:foo-bar) or separate via ';' character (?filter=foo:bar;baz:foo-bar)</para> + </note> + <example> + <title>Export only registry and pageManagement navigation nodes</title> + <programlisting>GET /mop/groupsites/platform/administrators/navigation.zip?filter=nav-uri:/administration/registry,/administration/pageManagement</programlisting> + </example> + <example> + <title>Export all site types but user and group</title> + <programlisting>GET /mop.zip?filter=site-type:!user,group</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-CommandLineInterfacex"> + + <title>Command Line Interface</title> + <para>The commands included in the management component provide us the tools to perform management operations on these MOP artifacts: site layout, pages, and navigation.</para> + <section id="sid-8094332_GateInManagement-ResourcePaths"> + + <title>Resource Paths</title> + <para>The paths of the MOP resources are exactly the same as the REST URL's (of course without the URL syntax). For example the path of the homepage for the classic site would be:</para> + <example> + <title>Example</title> + <programlisting>[ /]% cd /mop/portalsites/classic/pages/homepage + +[homepage]% pwd +/mop/portalsites/classic/pages/homepage</programlisting> + </example> + <note> + <title>Note</title> + <para>All resources/paths can be autocompleted by hitting the tab key.</para> + </note> + </section> + <section id="sid-8094332_GateInManagement-ExportandFiltering-2"> + + <title>Export and Filtering</title> + <para> + Filtering is activated when the + <code>filter</code> + attribute is passed to an + <code>export-resource</code> + operation. The filter attribute is a multi-value attribute that is passed to the CLI using the + <code>--filter</code> + attribute for the + <code>export</code> + command. + </para> + <example> + <title>Export all portal site types</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:portal /mop</programlisting> + </example> + <example> + <title>Export all sites types but user</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:!user /mop</programlisting> + </example> + <para>The option can be specified multiple times for multiple values.</para> + <example> + <title>Export only the /platform/administrators group site</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:group --filter site-name:/platform/administrators /mop</programlisting> + </example> + <para> + Also as discussed in the Path Templates section in this document, the filter attribute can separate different path templates by the + <code>;</code> + character. + </para> + <example> + <title>Export only pages named homepage, navigation named home for site classic</title> + <programlisting>export --file /tmp/classic.zip --filter page-name:homepage;nav-uri:home /mop/portalsites/classic</programlisting> + </example> + <important> + <title>Important</title> + <para>All three artifacts (site layout, navigation, and pages) are included in export by default. In other words if you don't specify their path template in the filter, the data will be included.</para> + </important> + </section> + </section> + </chapter>

13 years, 2 months

1
0
0 / 0

gatein SVN: r8062 - epp/docs/branches/5.2/Admin_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-14 20:31:46 -0500 (Mon, 14 Nov 2011) New Revision: 8062 Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml Log: Incorporating latest chenges from nscavelli Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-11-15 01:28:38 UTC (rev 8061) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-11-15 01:31:46 UTC (rev 8062) @@ -4,28 +4,28 @@ %BOOK_ENTITIES; ]> <bookinfo id="book-Admin_Guide-Admin_Guide"> - <title>Admin Guide</title> - <subtitle>For use with JBoss Enterprise Portal Platform 5</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.0</edition> - <pubsnumber>3</pubsnumber> - <abstract> - <para> - This document is a guide to administering an implementation of JBoss Enterprise Portal Platform. It is intended for System Administrators and assumes a high level of technical knowledge. - </para> + <title>Admin Guide</title> + <subtitle>For use with JBoss Enterprise Portal Platform 5</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>5.2</productnumber> + <edition>5.2.0</edition> + <pubsnumber>4</pubsnumber> + <abstract> + <para> + This document is a guide to administering an implementation of JBoss Enterprise Portal Platform. It is intended for System Administrators and assumes a high level of technical knowledge. + </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.png" format="PNG" /> - </imageobject> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.png" format="PNG" /> + </imageobject> - </inlinemediaobject> + </inlinemediaobject> - </corpauthor> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </corpauthor> + <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </bookinfo> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml 2011-11-15 01:28:38 UTC (rev 8061) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml 2011-11-15 01:31:46 UTC (rev 8062) @@ -4,48 +4,62 @@ %BOOK_ENTITIES; ]> <appendix id="appe-Admin_Guide-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>5.2.0-3</revnumber> - <date>Wed Oct 19 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>5.2.0-4</revnumber> + <date>Tue Nov 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Staged for beta release.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-3</revnumber> + <date>Wed Oct 19 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Added to brew system.</member> + </author> + <revdescription> + <simplelist> + <member>Added to brew system.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-1</revnumber> - <date>Wed Oct 12 2011</date> - <author> - <firstname>Nick</firstname> - <surname>Scavelli</surname> - <email>nscavell(a)redhat.com</email> + </revision> + <revision> + <revnumber>5.2.0-1</revnumber> + <date>Wed Oct 12 2011</date> + <author> + <firstname>Nick</firstname> + <surname>Scavelli</surname> + <email>nscavell(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Initial creation of book.</member> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> + </revision> - </revhistory> + </revhistory> - </simpara> + </simpara> </appendix>

13 years, 2 months

1
0
0 / 0

gatein SVN: r8061 - in epp/docs/branches/5.2/Release_Notes: en-US and 1 other directory.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-11-14 20:28:38 -0500 (Mon, 14 Nov 2011) New Revision: 8061 Added: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml Removed: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.2/Release_Notes/publican.cfg Log: Had to change the title so I could push the Beta Notes up for EPP Copied: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent (from rev 8056, epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent) =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent 2011-11-15 01:28:38 UTC (rev 8061) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Site Publisher"> + + +<!ENTITY BOOKID "Site Publisher Release Notes"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "5"> +<!ENTITY VY "5.2"> +<!ENTITY VZ "5.2.0"> Copied: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml (from rev 8056, epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml) =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml 2011-11-15 01:28:38 UTC (rev 8061) @@ -0,0 +1,274 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <chapter id="Release_Notes-Introduction"> + <title>Introduction</title> + <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. + </para> + <para>By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, </para> + <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> + </chapter> + <chapter> + <title>Upgraded Components</title> + <formalpara> + <title>New Components</title> + <para>The following new components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Site Migration Utilities</term> + <listitem> + <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Site Management Utilities</term> + <listitem> + <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> + </listitem> + </varlistentry> + </variablelist> + <formalpara> + <title>Updated Components</title> + <para>The following updated components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Java Content Respostory</term> + <listitem> + <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para> + </note> + </chapter> + <chapter id="Release_Notes-Component_Features"> + <title> + Component Versions + </title> + <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> + <table frame="all" pgwide="1"> + <title>Component Versions</title> + <tgroup cols="2" colsep="1"> + <colspec colnum="1"/> + <colspec colnum="2"/> + <thead> + <row> + <entry>Component</entry> + <entry>Version</entry> + </row> + </thead> + <tbody> + <row> + <entry>EAP</entry> + <entry>5.1.1-GA</entry> + </row> + <row> + <entry>eXo junit</entry> + <entry>1.2.1-GA</entry> + </row> + <row> + <entry>eXo kernel</entry> + <entry>2.3.3-GA</entry> + </row> + <row> + <entry>eXo Core</entry> + <entry>2.4.3-GA</entry> + </row> + <row> + <entry>eXo WS</entry> + <entry>2.2.3-GA</entry> + </row> + <row> + <entry>eXo JCR</entry> + <entry>1.14.3-GA</entry> + </row> + <row> + <entry>Apache Shindig</entry> + <entry>2.0.2</entry> + </row> + <row> + <entry>Simple Captcha</entry> + <entry>1.1.1-GA-Patch01</entry> + </row> + <row> + <entry>GateIn Parent</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn dep</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn Common</entry> + <entry>2.0.4-GA</entry> + </row> + <row> + <entry>GateIn WCI</entry> + <entry>2.1.0-GA</entry> + </row> + <row> + <entry>GateIn PC</entry> + <entry>2.3.0-GA</entry> + </row> + <row> + <entry>GateIn WSRP</entry> + <entry>2.1.0-EPP520-GA</entry> + </row> + <row> + <entry>GateIn MOP</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn SSO</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>PicketLink IDM</entry> + <entry>1.3.0.GA</entry> + </row> + <row> + <entry>Chromattic</entry> + <entry>1.1.1</entry> + </row> + <row> + <entry>Portlet Bridge</entry> + <entry>2.2.0.GA.EPP520</entry> + </row> + <row> + <entry>Seam</entry> + <entry>2.2.4.EAP5</entry> + </row> + <row> + <entry>Richfaces</entry> + <entry>3.3.1.SP3</entry> + </row> + <row> + <entry>Groovy</entry> + <entry>1.7.6</entry> + </row> + <row> + <entry>Commons DBCP</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons IO</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons Lang</entry> + <entry>2.6</entry> + </row> + <row> + <entry>HSQLDB</entry> + <entry>2.0.0</entry> + </row> + <row> + <entry>JBoss Cache</entry> + <entry>3.2.7</entry> + </row> + <row> + <entry>GateIn Management</entry> + <entry>1.0.0-GA</entry> + </row> + </tbody> + </tgroup> + </table> + </chapter> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_In_Production"> + <title> + Resolved Issues + </title> + <para> + The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title> + Known Issues + </title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. + </para> + </chapter> + <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> + <title> Product Support and License Website Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Support Processes</title> + <para> + <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> + <title> Production Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> + <title> Production Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> + <title> Developer Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> + <title> Developer Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> + <title> Product Update and Support Policy by Product </title> + <para> + <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title> JBoss End User License Agreement </title> + <para> + <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> + </para> + </formalpara> + </chapter> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book> Deleted: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent 2011-11-14 23:36:45 UTC (rev 8060) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent 2011-11-15 01:28:38 UTC (rev 8061) @@ -1,14 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Site Publisher"> - - -<!ENTITY BOOKID "Site Publisher Release Notes"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.0"> Deleted: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-11-14 23:36:45 UTC (rev 8060) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-11-15 01:28:38 UTC (rev 8061) @@ -1,245 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <chapter id="Release_Notes-Introduction"> - <title>Introduction</title> - <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. - </para> - <para>By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, </para> - <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> - </chapter> - <chapter> - <title>Upgraded Components</title> - <para><remark>What component upgrades deserve highlighting.</remark></para> - <note> - <para>For detailed information about component versions included in this release, refer to </para> - </note> - </chapter> - <chapter id="Release_Notes-Component_Features"> - <title> - <remark>Component Versions</remark> - </title> - <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> - <table frame="all" pgwide="1"> - <title>Component Versions</title> - <tgroup cols="2" colsep="1"> - <colspec colnum="1"/> - <colspec colnum="2"/> - <thead> - <row> - <entry>Component</entry> - <entry>Version</entry> - </row> - </thead> - <tbody> - <row> - <entry>EAP</entry> - <entry>5.1.1-GA</entry> - </row> - <row> - <entry>eXo junit</entry> - <entry>1.2.1-GA</entry> - </row> - <row> - <entry>eXo kernel</entry> - <entry>2.3.3-GA</entry> - </row> - <row> - <entry>eXo Core</entry> - <entry>2.4.3-GA</entry> - </row> - <row> - <entry>eXo WS</entry> - <entry>2.2.3-GA</entry> - </row> - <row> - <entry>eXo JCR</entry> - <entry>1.14.3-GA</entry> - </row> - <row> - <entry>Apache Shindig</entry> - <entry>2.0.2</entry> - </row> - <row> - <entry>Simple Captcha</entry> - <entry>1.1.1-GA-Patch01</entry> - </row> - <row> - <entry>GateIn Parent</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn dep</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn Common</entry> - <entry>2.0.4-GA</entry> - </row> - <row> - <entry>GateIn WCI</entry> - <entry>2.1.0-GA</entry> - </row> - <row> - <entry>GateIn PC</entry> - <entry>2.3.0-GA</entry> - </row> - <row> - <entry>GateIn WSRP</entry> - <entry>2.1.0-EPP520-GA</entry> - </row> - <row> - <entry>GateIn MOP</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn SSO</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>PicketLink IDM</entry> - <entry>1.3.0.GA</entry> - </row> - <row> - <entry>Chromattic</entry> - <entry>1.1.1</entry> - </row> - <row> - <entry>Portlet Bridge</entry> - <entry>2.2.0.GA.EPP520</entry> - </row> - <row> - <entry>Seam</entry> - <entry>2.2.4.EAP5</entry> - </row> - <row> - <entry>Richfaces</entry> - <entry>3.3.1.SP3</entry> - </row> - <row> - <entry>Groovy</entry> - <entry>1.7.6</entry> - </row> - <row> - <entry>Commons DBCP</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons IO</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons Lang</entry> - <entry>2.6</entry> - </row> - <row> - <entry>HSQLDB</entry> - <entry>2.0.0</entry> - </row> - <row> - <entry>JBoss Cache</entry> - <entry>3.2.7</entry> - </row> - <row> - <entry>GateIn Management</entry> - <entry>1.0.0-GA</entry> - </row> - </tbody> - </tgroup> - </table> - </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. - </para> - <para> - The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title> - <remark>Resolved Issues</remark> - </title> - <para> - The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> - </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title> - <remark>Known Issues</remark> - </title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. - </para> - </chapter> - <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product Support and License Website Links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Support Processes</title> - <para> - <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> - <title> Production Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> - <title> Production Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> - <title> Developer Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> - <title> Developer Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> - <title> Product Update and Support Policy by Product </title> - <para> - <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title> JBoss End User License Agreement </title> - <para> - <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> - </para> - </formalpara> - </chapter> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-11-14 23:36:45 UTC (rev 8060) +++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-11-15 01:28:38 UTC (rev 8061) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>5.2.0 Release Notes</title> + <title>5.2.0 BETA Release Notes</title> <subtitle>For use with JBoss Enterprise Portal Platform &VZ;.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-11-14 23:36:45 UTC (rev 8060) +++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-11-15 01:28:38 UTC (rev 8061) @@ -1,161 +1,89 @@ -<?xml version='1.0'?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> - - <variablelist> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1224" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1224"/> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is OPEN</remark> + <para> The Services Management Gadget currently has a display issue with the tabs displaying to the left of the table containing the data. This problem presented on Microsoft Internet Explorer 7 on Windows Vista. A fix is being investigated. </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1236"/> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is OPEN</remark> + <para> - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1236" /></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1258" /></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1258"/> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is OPEN</remark> + <para> Some CSS issues have been identified with the way the Portal home page is rendered. A fix is being investigated. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1271" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1271"/> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is OPEN</remark> + <para> When adding a portlet into a 2-column layout container, the container collapses while dragging the portlet into the container. The container sometimes remains collapsed after moving the portlet into the container. This problem presented on Microsoft Windows 7, using Internet Explorer 8. A fix is being investigated. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1345" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1345"/> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is OPEN</remark> + <para> An interface abnormality was discovered in the Account Portlet. If more than one instance of the Account Portlet is present on a page, tabs switching will work in the first portlet as designed. If tab switching is attempted in the other instances, the tab and the content in the portlet flashes temporarily, and the original tab is shown again. A fix is being investigated. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1351" /></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module does not have these options. This causes problems when a customer wants to implement SSO on a different portal container (for example in ecmdemo). No workaround exists for this issue. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1351"/> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is OPEN</remark> + <para> + The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module does not have these options. This causes problems when a customer wants to implement SSO on a different portal container (for example in ecmdemo). No workaround exists for this issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1352" /></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT only</title> - <para> - It was found that JBoss Web Services Native did not properly protect -against recursive entity resolution when processing Document Type -Definitions (DTD). A remote attacker could exploit this flaw by sending a -specially-crafted HTTP POST request to a deployed web service, causing -excessive CPU and memory consumption on the system hosting that service. If -the attack is repeated to consume all available network sockets, the server -will become unavailable. (CVE-2011-1483) - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1359" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1359"/> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is OPEN</remark> + <para> Sybase 15.5 imposes a limitation on the case used in portal names. Only lowercase portal names are supported. The problem does not present in Sybase 15.0.3. A fix is being investigated. </para> - - </listitem> - </varlistentry> - + </listitem> + </varlistentry> </variablelist> Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-11-14 23:36:45 UTC (rev 8060) +++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-11-15 01:28:38 UTC (rev 8061) @@ -4,7 +4,7 @@ xml_lang: en-US type: Book brand: JBoss -show_remarks: 1 +#show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist -cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__ +cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_BETA_Release_Notes-5.2-web-__LANG__

13 years, 2 months

1
0
0 / 0

gatein SVN: r8060 - epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/src/main/resources/deploy/gatein.ear/META-INF.

by do-not-reply＠jboss.org

Author: hfnukal Date: 2011-11-14 18:36:45 -0500 (Mon, 14 Nov 2011) New Revision: 8060 Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/src/main/resources/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml Log: JBEPP-1351 Use options in SSOLoginModule example in gatein-jboss-beans.xml Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/src/main/resources/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/src/main/resources/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml 2011-11-14 23:05:34 UTC (rev 8059) +++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/src/main/resources/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml 2011-11-14 23:36:45 UTC (rev 8060) @@ -32,10 +32,12 @@ </login-module> </authentication> -  +  <!-- <authentication> <login-module code="org.gatein.sso.agent.login.SSOLoginModule" flag="required"> + <module-option name="portalContainerName">portal</module-option> + <module-option name="realmName">gatein-domain</module-option> </login-module> <login-module code="org.exoplatform.services.security.j2ee.JbossLoginModule" flag="required"> <module-option name="portalContainerName">portal</module-option>

13 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits November 2011