December 2011 - gatein-commits - Jboss List Archives

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

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-12-13 20:55:47 -0500 (Tue, 13 Dec 2011) New Revision: 8249 Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_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/feature_requests.xml epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml epp/docs/branches/5.2/Release_Notes/publican.cfg Log: Final Changes committed for Release Notes 5.2.0 before GA 15th Dec Modified: 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-12-13 14:19:33 UTC (rev 8248) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-14 01:55:47 UTC (rev 8249) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> %BOOK_ENTITIES; ]> -<book status="draft"> +<book> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <chapter id="Release_Notes-Introduction"> <title>Introduction</title> @@ -229,14 +229,13 @@ 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> - <title> - <remark>NEEDINFO</remark> - </title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="need_info.xml"/> - </chapter>  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. -<note><para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para></note> +<note> + <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para> + </note> </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> Application registry categories are now cached for better performance. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> Each site can now have a site description, which can be accessed and used by the management applications. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container). </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> EPP is now partially available in Czech language. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> Cluster data transportation has been optimized to reduce the number of network connections and threads. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer. </para> - - </listitem> - </varlistentry> - + </listitem> + </varlistentry> </variablelist> 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-12-13 14:19:33 UTC (rev 8248) +++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-14 01:55:47 UTC (rev 8249) @@ -1,4 +1,116 @@ +<?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" [ +]> -<para> -There are no known issues in this release. -</para> + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1376">JBEPP-1376</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1396">JBEPP-1396</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When a dashboard page is created and its title translated in various languages, switching languages will not update the dashboard page name on the user interface immediately. To work around the issue, log out and log back in to show the correct translation for the page name. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1399">JBEPP-1399</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + If you create a system subnode under a node in the Navigation Management, you are allowed the delete the parent node without the "Cannot delete a system node" message being shown. When trying to save the result, a message "Unknown error" is shown and the following NPE is thrown. A fix is being investigated for a future release. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1401">JBEPP-1401</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with the No Result Found pop-up causes it to display after first searching for a non-existent user string, then searching for a string that is known to exist. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1402">JBEPP-1402</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1411">JBEPP-1411</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + System child nodes can be deleted if the parent node is deleted. A system node should not be able to de be deleted, regardless of its position in a navigation tree. This behavior will be fixed in a future release. + </para> + + </listitem> + </varlistentry> + +</variablelist> Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-13 14:19:33 UTC (rev 8248) +++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-14 01:55:47 UTC (rev 8249) @@ -1,626 +1,389 @@ -<?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-348">JBEPP-348</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink></term> - <listitem> - - <remark>Assignee is: bdaw</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing. Now users cannot add restricted gadget. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink></term> - <listitem> - - <remark>Assignee is: mputz</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink> + </term> + <listitem> + <remark>Assignee is: mputz</remark> + <remark>JIRA is Closed</remark> + <para> An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended. </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf". - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf". - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink></term> - <listitem> - - <remark>Assignee is: kenfinni</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink> + </term> + <listitem> + <remark>Assignee is: kenfinni</remark> + <remark>JIRA is Closed</remark> + <para> org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> It was found that the invoker servlets, deployed by default via httpha-invoker, only performed access control on the HTTP GET and POST methods, allowing remote attackers to make unauthenticated requests by @@ -629,102 +392,66 @@ default installations unless an administrator has misconfigured the security interceptor or disabled it. (CVE-2011-4085) </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink></term> - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is Closed</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs. </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is Closed</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 did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</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 did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile. </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is Closed</remark> - - - <para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security. </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-12-13 14:19:33 UTC (rev 8248) +++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-14 01:55:47 UTC (rev 8249) @@ -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__

13 years

1
0
0 / 0

gatein SVN: r8248 - components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-12-13 09:19:33 -0500 (Tue, 13 Dec 2011) New Revision: 8248 Modified: components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties Log: - GTNWSRP-275: fixed invalid values. Modified: components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties =================================================================== --- components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 14:18:00 UTC (rev 8247) +++ components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 14:19:33 UTC (rev 8248) @@ -143,7 +143,7 @@ consumers_table_reload=Recharger consommateurs CONSUMER_TYPE=Consommateur DUPLICATE_ERROR=Un {1} nomm\u00e9 ''{0}'' existe d\u00e9j\u00e0! -INVALID_NAME_ERROR=''{0}'' est un nom ou une valuer invalide pour un {1} \: Ne peut pas u00eatre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '\=' ou '%5c' +INVALID_NAME_ERROR=''{0}'' est un nom ou une valeur invalide pour un {1} : Ne peut pas �tre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '=' ou '%5c' edit_consumer_timeout=Timeout des op�rations WS: edit_consumer_timeout_milliseconds=(millisecondes avant timeout) consumers_table_action_import=Importer @@ -185,4 +185,4 @@ producer_config_wsdl_v2=Adresse WSDL pour le Producteur WSRP v2: unavailable_service=Le service WSRP n''est pas disponible. Veuillez l''activer avant d'utiliser cette portlet. bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. -REGISTRATION_PROPERTY_TYPE=propriu00e9tu00e9 d'enregistrement \ No newline at end of file +REGISTRATION_PROPERTY_TYPE=propri�t� d'enregistrement \ No newline at end of file

13 years

1
0
0 / 0

gatein SVN: r8247 - components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-12-13 09:18:00 -0500 (Tue, 13 Dec 2011) New Revision: 8247 Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties Log: - GTNWSRP-275: fixed invalid value. Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 14:10:11 UTC (rev 8246) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 14:18:00 UTC (rev 8247) @@ -185,4 +185,4 @@ producer_config_wsdl_v2=Adresse WSDL pour le Producteur WSRP v2: unavailable_service=Le service WSRP n''est pas disponible. Veuillez l''activer avant d'utiliser cette portlet. bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. -REGISTRATION_PROPERTY_TYPE=propriu00e9tu00e9 d'enregistrement \ No newline at end of file +REGISTRATION_PROPERTY_TYPE=propri�t� d'enregistrement \ No newline at end of file

13 years

1
0
0 / 0

gatein SVN: r8246 - in components/wsrp/branches/2.1.x: admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet and 2 other directories.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-12-13 09:10:11 -0500 (Tue, 13 Dec 2011) New Revision: 8246 Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/jsf/producer/producer.xhtml components/wsrp/branches/2.1.x/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java Log: - GTNWSRP-275: made ProducerBean implement registration property name/hint/label validation. Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java 2011-12-13 14:10:11 UTC (rev 8246) @@ -1,6 +1,6 @@ /* * JBoss, a division of Red Hat - * Copyright 2009, Red Hat Middleware, LLC, and individual + * Copyright 2011, Red Hat Middleware, LLC, and individual * contributors as indicated by the @authors tag. See the * copyright.txt in the distribution for a full listing of * individual contributors. @@ -43,6 +43,11 @@ public String getAsString(FacesContext facesContext, UIComponent uiComponent, Object o) { - return o == null ? null : ((LocalizedString)o).getValue(); + return getAsString(o); } + + static String getAsString(Object localizedString) + { + return localizedString == null ? null : ((LocalizedString)localizedString).getValue(); + } } Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java 2011-12-13 14:10:11 UTC (rev 8246) @@ -30,14 +30,17 @@ import org.gatein.wsrp.producer.config.ProducerConfigurationService; import org.gatein.wsrp.producer.config.ProducerRegistrationRequirements; import org.gatein.wsrp.producer.config.impl.ProducerRegistrationRequirementsImpl; +import org.gatein.wsrp.registration.LocalizedString; import org.gatein.wsrp.registration.RegistrationPropertyDescription; +import javax.faces.application.FacesMessage; import javax.faces.component.UIComponent; import javax.faces.component.html.HtmlDataTable; import javax.faces.context.FacesContext; import javax.faces.event.ActionEvent; import javax.faces.event.ValueChangeEvent; import javax.faces.model.SelectItem; +import javax.faces.validator.ValidatorException; import javax.xml.namespace.QName; import java.io.Serializable; import java.util.ArrayList; @@ -53,6 +56,7 @@ */ public class ProducerBean extends ManagedBean implements Serializable { + private static final String REGISTRATION_PROPERTY_TYPE = "REGISTRATION_PROPERTY_TYPE"; private transient ProducerConfigurationService configurationService; private String policyClassName; private String validatorClassName; @@ -285,12 +289,13 @@ protected String getObjectTypeName() { - return null; // default implementation as not used + return REGISTRATION_PROPERTY_TYPE; } public boolean isAlreadyExisting(String objectName) { - return false; // default implementation as not used + // allow for edit of properties since they will be replaced anyway + return false; } private LocalProducerConfiguration getLocalConfiguration() @@ -315,6 +320,25 @@ return beanContext.getServerAddress() + "/wsrp-producer/v2/MarkupService?wsdl"; } + public void validate(FacesContext facesContext, UIComponent uiComponent, Object o) + { + String toValidate = null; + if (o instanceof String) + { + toValidate = (String)o; + } + else if (o instanceof LocalizedString) + { + toValidate = LocalizedStringConverter.getAsString(o); + } + + final String validated = this.checkNameValidity(toValidate, uiComponent.getClientId(facesContext)); + if (validated == null) + { + throw new ValidatorException(new FacesMessage()); // need a non-null FacesMessage to avoid NPE + } + } + private static class LocalProducerConfiguration { private List<RegistrationPropertyDescription> registrationProperties; Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties 2011-12-13 14:10:11 UTC (rev 8246) @@ -177,6 +177,7 @@ bean_support_unexpected_error = An unexpected error occured: bean_support_cause = Cause: CONSUMER_TYPE = Consumer +REGISTRATION_PROPERTY_TYPE = registration property # ConsumerBean bean_consumer_null_id = No identifier was specified to resolve a consumer from. Please refresh the app and try again. @@ -221,6 +222,6 @@ org.jboss.portal.object.name.admin.WSRP=WSRP -INVALID_NAME_ERROR=''{0}'' is an invalid {1} name: Cannot be null, empty or contain '/', '.', '\\', '<', '>', '(', ')', '=' or '%5c' +INVALID_NAME_ERROR=''{0}'' is an invalid {1} name or value: Cannot be null, empty or contain '/', '.', '\\', '<', '>', '(', ')', '=' or '%5c' DUPLICATE_ERROR=A {1} named ''{0}'' already exists! unavailable_service = WSRP service is unavailble. Please activate it before using this portlet. Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 14:10:11 UTC (rev 8246) @@ -143,7 +143,7 @@ consumers_table_reload=Recharger consommateurs CONSUMER_TYPE=Consommateur DUPLICATE_ERROR=Un {1} nomm\u00e9 ''{0}'' existe d\u00e9j\u00e0! -INVALID_NAME_ERROR=''{0}'' est un nom invalide pour un {1} : Ne peut pas \u00eatre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '=' ou '%5c' +INVALID_NAME_ERROR=''{0}'' est un nom ou une valeur invalide pour un {1} : Ne peut pas \u00eatre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '=' ou '%5c' edit_consumer_timeout=Timeout des op�rations WS: edit_consumer_timeout_milliseconds=(millisecondes avant timeout) consumers_table_action_import=Importer @@ -184,4 +184,5 @@ producer_config_wsdl_v1=Adresse WSDL pour le Producteur WSRP v1: producer_config_wsdl_v2=Adresse WSDL pour le Producteur WSRP v2: unavailable_service=Le service WSRP n''est pas disponible. Veuillez l''activer avant d'utiliser cette portlet. -bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. \ No newline at end of file +bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. +REGISTRATION_PROPERTY_TYPE=propriu00e9tu00e9 d'enregistrement \ No newline at end of file Modified: components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/jsf/producer/producer.xhtml =================================================================== --- components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/jsf/producer/producer.xhtml 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/admin-gui/src/main/webapp/jsf/producer/producer.xhtml 2011-12-13 14:10:11 UTC (rev 8246) @@ -111,7 +111,8 @@ styleClass="UIGrid ConsumerGrid" width="100%"> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_name}</f:facet> - <h:inputText id="name" value="#{property.nameAsString}" size="21"/> + <h:inputText id="name" value="#{property.nameAsString}" validator="#{producer.validate}" + size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_type}</f:facet> @@ -121,11 +122,11 @@ </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_label}</f:facet> - <h:inputText id="label" value="#{property.label}" size="21"/> + <h:inputText id="label" value="#{property.label}" validator="#{producer.validate}" size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_hint}</f:facet> - <h:inputText id="hint" value="#{property.hint}" size="21"/> + <h:inputText id="hint" value="#{property.hint}" validator="#{producer.validate}" size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_action}</f:facet> Modified: components/wsrp/branches/2.1.x/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java =================================================================== --- components/wsrp/branches/2.1.x/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java 2011-12-13 13:54:37 UTC (rev 8245) +++ components/wsrp/branches/2.1.x/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java 2011-12-13 14:10:11 UTC (rev 8246) @@ -38,6 +38,14 @@ */ public class RegistrationPropertyDescription implements PropertyDescription { + public static final ParameterValidation.ValidationErrorHandler HANDLER = new ParameterValidation.ValidationErrorHandler(null) + { + @Override + protected String internalValidationErrorHandling(String failedValue) + { + throw new IllegalArgumentException(failedValue + " is not a valid RegistrationPropertyDescription name"); + } + }; private String key; private QName name; private QName type; @@ -173,7 +181,8 @@ public void setNameAsString(String name) { - setName(new QName(name)); + final String sanitizedName = ParameterValidation.sanitizeFromPatternWithHandler(name, ParameterValidation.XSS_CHECK, HANDLER); + setName(new QName(sanitizedName)); } public String getNameAsString()

13 years

1
0
0 / 0

gatein SVN: r8245 - in components/wsrp/trunk: admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet and 2 other directories.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-12-13 08:54:37 -0500 (Tue, 13 Dec 2011) New Revision: 8245 Modified: components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties components/wsrp/trunk/admin-gui/src/main/webapp/jsf/producer/producer.xhtml components/wsrp/trunk/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java Log: - GTNWSRP-275: made ProducerBean implement registration property name/hint/label validation. Modified: components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java =================================================================== --- components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/LocalizedStringConverter.java 2011-12-13 13:54:37 UTC (rev 8245) @@ -1,6 +1,6 @@ /* * JBoss, a division of Red Hat - * Copyright 2009, Red Hat Middleware, LLC, and individual + * Copyright 2011, Red Hat Middleware, LLC, and individual * contributors as indicated by the @authors tag. See the * copyright.txt in the distribution for a full listing of * individual contributors. @@ -43,6 +43,11 @@ public String getAsString(FacesContext facesContext, UIComponent uiComponent, Object o) { - return o == null ? null : ((LocalizedString)o).getValue(); + return getAsString(o); } + + static String getAsString(Object localizedString) + { + return localizedString == null ? null : ((LocalizedString)localizedString).getValue(); + } } Modified: components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java =================================================================== --- components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ProducerBean.java 2011-12-13 13:54:37 UTC (rev 8245) @@ -30,14 +30,17 @@ import org.gatein.wsrp.producer.config.ProducerConfigurationService; import org.gatein.wsrp.producer.config.ProducerRegistrationRequirements; import org.gatein.wsrp.producer.config.impl.ProducerRegistrationRequirementsImpl; +import org.gatein.wsrp.registration.LocalizedString; import org.gatein.wsrp.registration.RegistrationPropertyDescription; +import javax.faces.application.FacesMessage; import javax.faces.component.UIComponent; import javax.faces.component.html.HtmlDataTable; import javax.faces.context.FacesContext; import javax.faces.event.ActionEvent; import javax.faces.event.ValueChangeEvent; import javax.faces.model.SelectItem; +import javax.faces.validator.ValidatorException; import javax.xml.namespace.QName; import java.io.Serializable; import java.util.ArrayList; @@ -53,6 +56,7 @@ */ public class ProducerBean extends ManagedBean implements Serializable { + private static final String REGISTRATION_PROPERTY_TYPE = "REGISTRATION_PROPERTY_TYPE"; private transient ProducerConfigurationService configurationService; private String policyClassName; private String validatorClassName; @@ -285,12 +289,13 @@ protected String getObjectTypeName() { - return null; // default implementation as not used + return REGISTRATION_PROPERTY_TYPE; } public boolean isAlreadyExisting(String objectName) { - return false; // default implementation as not used + // allow for edit of properties since they will be replaced anyway + return false; } private LocalProducerConfiguration getLocalConfiguration() @@ -315,6 +320,25 @@ return beanContext.getServerAddress() + "/wsrp-producer/v2/MarkupService?wsdl"; } + public void validate(FacesContext facesContext, UIComponent uiComponent, Object o) + { + String toValidate = null; + if (o instanceof String) + { + toValidate = (String)o; + } + else if (o instanceof LocalizedString) + { + toValidate = LocalizedStringConverter.getAsString(o); + } + + final String validated = this.checkNameValidity(toValidate, uiComponent.getClientId(facesContext)); + if (validated == null) + { + throw new ValidatorException(new FacesMessage()); // need a non-null FacesMessage to avoid NPE + } + } + private static class LocalProducerConfiguration { private List<RegistrationPropertyDescription> registrationProperties; Modified: components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties =================================================================== --- components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource.properties 2011-12-13 13:54:37 UTC (rev 8245) @@ -177,6 +177,7 @@ bean_support_unexpected_error = An unexpected error occured: bean_support_cause = Cause: CONSUMER_TYPE = Consumer +REGISTRATION_PROPERTY_TYPE = registration property # ConsumerBean bean_consumer_null_id = No identifier was specified to resolve a consumer from. Please refresh the app and try again. @@ -221,6 +222,6 @@ org.jboss.portal.object.name.admin.WSRP=WSRP -INVALID_NAME_ERROR=''{0}'' is an invalid {1} name: Cannot be null, empty or contain '/', '.', '\\', '<', '>', '(', ')', '=' or '%5c' +INVALID_NAME_ERROR=''{0}'' is an invalid {1} name or value: Cannot be null, empty or contain '/', '.', '\\', '<', '>', '(', ')', '=' or '%5c' DUPLICATE_ERROR=A {1} named ''{0}'' already exists! unavailable_service = WSRP service is unavailble. Please activate it before using this portlet. Modified: components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties =================================================================== --- components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/admin-gui/src/main/webapp/WEB-INF/classes/locale/portlet/Resource_fr.properties 2011-12-13 13:54:37 UTC (rev 8245) @@ -143,7 +143,7 @@ consumers_table_reload=Recharger consommateurs CONSUMER_TYPE=Consommateur DUPLICATE_ERROR=Un {1} nomm\u00e9 ''{0}'' existe d\u00e9j\u00e0! -INVALID_NAME_ERROR=''{0}'' est un nom invalide pour un {1} : Ne peut pas \u00eatre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '=' ou '%5c' +INVALID_NAME_ERROR=''{0}'' est un nom ou une valuer invalide pour un {1} \: Ne peut pas u00eatre null, vide ou contenir '/', '.', '\\', '<', '>', '(', ')', '\=' ou '%5c' edit_consumer_timeout=Timeout des op�rations WS: edit_consumer_timeout_milliseconds=(millisecondes avant timeout) consumers_table_action_import=Importer @@ -184,4 +184,5 @@ producer_config_wsdl_v1=Adresse WSDL pour le Producteur WSRP v1: producer_config_wsdl_v2=Adresse WSDL pour le Producteur WSRP v2: unavailable_service=Le service WSRP n''est pas disponible. Veuillez l''activer avant d'utiliser cette portlet. -bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. \ No newline at end of file +bean_consumer_null_id=Aucun identifiant disponible pour r�cup�rer un consommateur. Veuillez rafra�chir l'application et r�essayer. +REGISTRATION_PROPERTY_TYPE=propriu00e9tu00e9 d'enregistrement \ No newline at end of file Modified: components/wsrp/trunk/admin-gui/src/main/webapp/jsf/producer/producer.xhtml =================================================================== --- components/wsrp/trunk/admin-gui/src/main/webapp/jsf/producer/producer.xhtml 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/admin-gui/src/main/webapp/jsf/producer/producer.xhtml 2011-12-13 13:54:37 UTC (rev 8245) @@ -111,7 +111,8 @@ styleClass="UIGrid ConsumerGrid" width="100%"> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_name}</f:facet> - <h:inputText id="name" value="#{property.nameAsString}" size="21"/> + <h:inputText id="name" value="#{property.nameAsString}" validator="#{producer.validate}" + size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_type}</f:facet> @@ -121,11 +122,11 @@ </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_label}</f:facet> - <h:inputText id="label" value="#{property.label}" size="21"/> + <h:inputText id="label" value="#{property.label}" validator="#{producer.validate}" size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_hint}</f:facet> - <h:inputText id="hint" value="#{property.hint}" size="21"/> + <h:inputText id="hint" value="#{property.hint}" validator="#{producer.validate}" size="21"/> </h:column> <h:column> <f:facet name="header">#{i18n.producer_config_reg_prop_action}</f:facet> Modified: components/wsrp/trunk/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java =================================================================== --- components/wsrp/trunk/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java 2011-12-13 11:31:04 UTC (rev 8244) +++ components/wsrp/trunk/common/src/main/java/org/gatein/wsrp/registration/RegistrationPropertyDescription.java 2011-12-13 13:54:37 UTC (rev 8245) @@ -38,6 +38,14 @@ */ public class RegistrationPropertyDescription implements PropertyDescription { + public static final ParameterValidation.ValidationErrorHandler HANDLER = new ParameterValidation.ValidationErrorHandler(null) + { + @Override + protected String internalValidationErrorHandling(String failedValue) + { + throw new IllegalArgumentException(failedValue + " is not a valid RegistrationPropertyDescription name"); + } + }; private String key; private QName name; private QName type; @@ -173,7 +181,8 @@ public void setNameAsString(String name) { - setName(new QName(name)); + final String sanitizedName = ParameterValidation.sanitizeFromPatternWithHandler(name, ParameterValidation.XSS_CHECK, HANDLER); + setName(new QName(sanitizedName)); } public String getNameAsString()

13 years

1
0
0 / 0

gatein SVN: r8244 - components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-12-13 06:31:04 -0500 (Tue, 13 Dec 2011) New Revision: 8244 Modified: components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ConsumerBean.java Log: - Optimization. Modified: components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ConsumerBean.java =================================================================== --- components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ConsumerBean.java 2011-12-13 07:25:12 UTC (rev 8243) +++ components/wsrp/trunk/admin-gui/src/main/java/org/gatein/wsrp/admin/ui/ConsumerBean.java 2011-12-13 11:31:04 UTC (rev 8244) @@ -531,7 +531,7 @@ public boolean isAlreadyExisting(String objectName) { - return getRegistry().getConsumer(objectName) != null; + return getRegistry().containsConsumer(objectName); } public ConsumerRegistry getRegistry()

13 years

1
0
0 / 0

gatein SVN: r8243 - epp/docs/branches/5.2/Installation_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-13 02:25:12 -0500 (Tue, 13 Dec 2011) New Revision: 8243 Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml Log: JBEPP-1431: Actioning QA feedback. Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>3</pubsnumber> + <pubsnumber>4</pubsnumber> <abstract> <para> This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform. It forms part of the complete document suite along with the <emphasis role="bold">User Guide</emphasis> and <emphasis role="bold">Reference Guide</emphasis> available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." />. Modified: epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -97,14 +97,15 @@ </itemizedlist> <para> The default property file would look like the following: -<programlisting># Data -gatein.data.dir=/mnt/shared/mylocation +<programlisting># +gatein.conf.dir=${jboss.server.home.dir}/conf/gatein +gatein.data.dir=${jboss.server.data.dir}/gatein # DB gatein.db.data.dir=${gatein.data.dir}/db # JCR -gatein.jcr.config.type=cluster +gatein.jcr.config.type=local gatein.jcr.datasource.name=java:gatein-jcr gatein.jcr.datasource.dialect=auto @@ -113,7 +114,7 @@ gatein.jcr.cache.config=war:/conf/jcr/jbosscache/${gatein.jcr.config.type}/config.xml gatein.jcr.lock.cache.config=war:/conf/jcr/jbosscache/${gatein.jcr.config.type}/lock-config.xml gatein.jcr.index.data.dir=${gatein.jcr.data.dir}/lucene -gatein.jcr.index.changefilterclass=org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter +gatein.jcr.index.changefilterclass=org.exoplatform.services.jcr.impl.core.query.DefaultChangesFilter gatein.jcr.index.cache.config=war:/conf/jcr/jbosscache/cluster/indexer-config.xml gatein.jcr.jgroups.config=classpath:/jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml gatein.jcr.workspace.default=collaboration Modified: epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -41,7 +41,7 @@ datasource descriptor located at <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein-ds.xml</filename>: <programlisting language="XML" role="XML"> -<local-tx-datasource> +<no-tx-datasource> <jndi-name>gatein-jcr</jndi-name> <connection-url> jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-jcr-localDB @@ -54,7 +54,7 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> -</local-tx-datasource> +</no-tx-datasource> </programlisting> </para> @@ -82,7 +82,7 @@ datasource descriptor located at <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein-ds.xml</filename>: <programlisting language="XML" role="XML"> -<local-tx-datasource> +<no-tx-datasource> <jndi-name>gatein-idm</jndi-name> <connection-url> jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-idm-localDB @@ -95,7 +95,7 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> -</local-tx-datasource> +</no-tx-datasource> </programlisting> </para> @@ -175,7 +175,7 @@ </para> <note><title>Note: Database names</title> <para> - The remainder of this guide, and the configuration examples that follow assume the database names to be gateinjcr and gateinidm. If you change the database names, please update gatein-ds.xml accordingly (for each server configuration used). + The remainder of this guide, and the configuration examples that follow assume the database names to be gateinjcr and gateinidm. If you change the database names, please update <filename>gatein-ds.xml</filename> accordingly (for each server configuration used). </para> </note> <para> @@ -309,7 +309,7 @@ <para><filename>gatein-ds.xml</filename> will then look like:</para> <programlisting language="XML" role="XML"><![CDATA[<datasources> - <local-tx-datasource> + <no-tx-datasource> <jndi-name>gatein-idm</jndi-name> <connection-url>jdbc:mysql://mysql-hostname:3306/gateinidm</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> @@ -320,9 +320,9 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> - </local-tx-datasource> + </no-tx-datasource> - <local-tx-datasource> + <no-tx-datasource> <jndi-name>gatein-jcr</jndi-name> <connection-url>jdbc:mysql://mysql-hostname:3306/gateinjcr</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> @@ -333,7 +333,7 @@ <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> - </local-tx-datasource> + </no-tx-datasource> </datasources>]]> </programlisting> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -5,7 +5,7 @@ ]> <chapter id="Getting_Started"> - <title>Getting Started</title> + <title>Getting Started</title> <section id="sect-Installation_Guide-Getting_Started-Upgrading_Previous_Installations"> <title>Upgrading and Add-ons</title> @@ -15,16 +15,16 @@ <important> <title>Upgrading JBoss Enterprise Portal Platform</title> <para> - It is possible to upgrade from JBoss Enterprise Portal Platform version 5.0 or 5.1.0 to JBoss Enterprise Portal Platform 5.1.1. + It is possible to upgrade from JBoss Enterprise Portal Platform version 5.0 or 5.1.0 to JBoss Enterprise Portal Platform &VZ;. </para> <para> - To upgrade, copy any customized configuration files and database settings from your existing JBoss Enterprise Portal Platform installation to the corresponding location of the 5.1.1 installation. + To upgrade, copy any customized configuration files and database settings from your existing JBoss Enterprise Portal Platform installation to the corresponding location of the &VZ; installation. </para> </important> <important> <title>Add-ons</title> <para> - The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. + The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. </para> <itemizedlist> <listitem> @@ -37,475 +37,491 @@ Likewise, Site Publisher <emphasis role="bold">cannot</emphasis> be installed onto JBoss Enterprise Portal Platform 5.0 or 5.0.1 versions (including installations that include the technical preview release of the Site Publisher extension). </para> <para> - You must deploy a new instance of JBoss Enterprise Portal Platform 5.1.1 in order to use the Site Publisher add-on. + You must deploy a new instance of JBoss Enterprise Portal Platform &VZ; in order to use the Site Publisher add-on. </para> </listitem> </itemizedlist> </important> - </section> + </section> - <section id="Getting_Started-Pre_Requisites"> - <title>Pre-Requisites</title> - <para> - You must have adequate disk space to install a JDK and JBoss Enterprise Portal Platform (about 550MB) while also allowing enough space for your applications. Before installing JBoss Enterprise Portal Platform you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. - </para> - <section id="Pre_Requisites-EAP"> - <title>Enterprise Application Platform</title> - <para>JBoss Enterprise Portal Platform is built upon JBoss Enterprise Application Platform. For more details about the underlying platform please refer to - the EAP installation guide available at: <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/i..."></ulink> - </para> + <section id="Getting_Started-Pre_Requisites"> + <title>Pre-Requisites</title> + <para> + You must have adequate disk space to install a JDK and JBoss Enterprise Portal Platform (about 550MB) while also allowing enough space for your applications. Before installing JBoss Enterprise Portal Platform you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. + </para> + <section id="Pre_Requisites-EAP"> + <title>Enterprise Application Platform</title> + <para>JBoss Enterprise Portal Platform is built upon JBoss Enterprise Application Platform. For more details about the underlying platform please refer to + the EAP installation guide available at: <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/i..."></ulink> + </para> </section> - <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> - <title>System Requirements</title> - <formalpara> - <title>Minimum Installation Requirements</title> - <para> - The minimum hard disk space required to support the installation of the JBoss Enterprise Portal Platform is about 550MB. Additional space is required for the installation of the JDK upon which the JBoss Application Server depends. The JDK installation size is currently up to 150MB. - </para> - </formalpara> - <formalpara> - <title>Minimum Operational Requirements</title> - <para> - The minimum hardware required to support an operational JBoss Application Server varies depending on the following: - </para> - </formalpara> - <itemizedlist> - <listitem> - <para> - The size and complexity of the applications being served; - </para> - </listitem> - <listitem> - <para> - The demand placed on the server by the number and frequency of client requests; - </para> - </listitem> - <listitem> - <para> - The server configuration including the selected log files, their designated size and general server tuning. - </para> - </listitem> - </itemizedlist> - <para> - The following discussion relates to the deployment of a simple application on a server experiencing minimal demand. In view of this, the absolute minimum requirements for an operational server are: - </para> - <itemizedlist> - <listitem> - <para> - Disk Space: 1.5 GB - </para> - <itemizedlist> - <listitem> - <para> - The default server log file storage configuration is 500MB. - </para> - </listitem> - <listitem> - <para> - The remaining 500 MB is allocated to the server installation (240 MB), the required JDK (150 MB) and some additional space for applications (110 MB). - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para> - CPU: Intel Pentium Processor @ 1GHz - </para> - <itemizedlist> - <listitem> - <para> - Core 2 Duo, Core 2 Quad and Intel Xeon chips will improve the performance of servers which experience high demand. - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para> - RAM: 1.5 GB - </para> - <itemizedlist> - <listitem> - <para> - RAM installations of 2 GB or more will be required to run a server upon which small to medium applications are deployed. 4 GB or more is preferable for larger applications or to run a GUI server interface. - </para> - </listitem> - </itemizedlist> - </listitem> - </itemizedlist> - <important> - <para> - A server's performance must be viewed in light of the applications deployed on the server, the demand placed on the server by client requests and any post-installation server configuration or tuning. - </para> - </important> - <formalpara> - <title>Supported Installations</title> - <para> - For the latest information on supported Operating System / JVM combinations and supported Database platforms, please always refer to <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink>. - </para> - </formalpara> - <para> - The following is a list of certified operating systems and JVM version combinations: - </para> - <indexterm> - <primary>System Requirements</primary> - <secondary>OS/JVM</secondary> - </indexterm> - <table> - <title> - Supported Operating System / JVM Combinations. - </title> - <tgroup cols="2"> - <colspec colnum="1" colname="OS" colwidth="1*"></colspec> - <colspec colnum="2" colname="JVM" colwidth="1*"></colspec> - - <thead> - <row> - <entry> - <emphasis>Operating System</emphasis> - </entry> - <entry> - <emphasis>JVM Version</emphasis> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - OpenJDK 1.6.0-b09 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86 - </entry> - <entry> - IBM JDK 1.6.0 SR5 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - OpenJDK 1.6.0-b09 - </entry> - </row> - <row> - <entry> - Red Hat Enterprise Linux 5 x86_64 - </entry> - <entry> - IBM JDK 1.6.0 SR5 - </entry> - </row> - <row> - <entry> - Microsoft Windows 2008 x86 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Microsoft Windows 2008 x86_64 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - <row> - <entry> - Solaris 10 - </entry> - <entry> - Sun JVM 1.6 Update 15 - </entry> - </row> - </tbody> - </tgroup> - </table> - - <para> + <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements"> + <title>System Requirements</title> + <formalpara> + <title>Minimum Installation Requirements</title> + <para> + The minimum hard disk space required to support the installation of the JBoss Enterprise Portal Platform is about 550MB. Additional space is required for the installation of the JDK upon which the JBoss Application Server depends. The JDK installation size is currently up to 150MB. + </para> + </formalpara> + <formalpara> + <title>Minimum Operational Requirements</title> + <para> + The minimum hardware required to support an operational JBoss Application Server varies depending on the following: + </para> + </formalpara> + <itemizedlist> + <listitem> + <para> + The size and complexity of the applications being served; + </para> + </listitem> + <listitem> + <para> + The demand placed on the server by the number and frequency of client requests; + </para> + </listitem> + <listitem> + <para> + The server configuration including the selected log files, their designated size and general server tuning. + </para> + </listitem> + </itemizedlist> + <para> + The following discussion relates to the deployment of a simple application on a server experiencing minimal demand. In view of this, the absolute minimum requirements for an operational server are: + </para> + <itemizedlist> + <listitem> + <para> + Disk Space: 1.5 GB + </para> + <itemizedlist> + <listitem> + <para> + The default server log file storage configuration is 500MB. + </para> + </listitem> + <listitem> + <para> + The remaining 500 MB is allocated to the server installation (240 MB), the required JDK (150 MB) and some additional space for applications (110 MB). + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + CPU: Intel Pentium Processor @ 1GHz + </para> + <itemizedlist> + <listitem> + <para> + Core 2 Duo, Core 2 Quad and Intel Xeon chips will improve the performance of servers which experience high demand. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + RAM: 1.5 GB + </para> + <itemizedlist> + <listitem> + <para> + RAM installations of 2 GB or more will be required to run a server upon which small to medium applications are deployed. 4 GB or more is preferable for larger applications or to run a GUI server interface. + </para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + <important> + <para> + A server's performance must be viewed in light of the applications deployed on the server, the demand placed on the server by client requests and any post-installation server configuration or tuning. + </para> + </important> + <formalpara> + <title>Supported Installations</title> + <para> + For the latest information on supported Operating System / JVM combinations and supported Database platforms, please always refer to <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink>. + </para> + </formalpara> + <para> + The following is a list of certified operating systems and JVM version combinations: + </para> + <indexterm> + <primary>System Requirements</primary> + <secondary>OS/JVM</secondary> + </indexterm> + <table> + <title> + Supported Operating System / JVM Combinations. + </title> + <tgroup cols="2"> + <colspec colnum="1" colname="OS" colwidth="1*"></colspec> + <colspec colnum="2" colname="JVM" colwidth="1*"></colspec> + + <thead> + <row> + <entry> + <emphasis>Operating System</emphasis> + </entry> + <entry> + <emphasis>JVM Version</emphasis> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Red Hat Enterprise Linux 6 + </entry> + <entry> + OpenJDK + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 6 + </entry> + <entry> + SunJDK + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + OpenJDK 1.6.0-b09 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86 + </entry> + <entry> + IBM JDK 1.6.0 SR5 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + OpenJDK 1.6.0-b09 + </entry> + </row> + <row> + <entry> + Red Hat Enterprise Linux 5 x86_64 + </entry> + <entry> + IBM JDK 1.6.0 SR5 + </entry> + </row> + <row> + <entry> + Microsoft Windows 2008 x86 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Microsoft Windows 2008 x86_64 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + <row> + <entry> + Solaris 10 + </entry> + <entry> + Sun JVM 1.6 Update 15 + </entry> + </row> + </tbody> + </tgroup> + </table> + + <para> The following is a cumulative table of supported databases and JDBC drivers. </para> <para> Entries shown for each release are supported <emphasis role="bold">in addition to those in previous releases</emphasis>: - </para> - <indexterm> - <primary>System Requirements</primary> - <secondary>Database</secondary> - </indexterm> - <indexterm> - <primary>Database</primary> - <secondary>System Requirements</secondary> - </indexterm> - <table> - <title>Supported Database and JDBC driver Combinations</title> - <tgroup cols="2"> - <colspec colnum="1" colname="c1" colwidth="1*"></colspec> - <colspec colnum="2" colname="c2" colwidth="1*"></colspec> + </para> + <indexterm> + <primary>System Requirements</primary> + <secondary>Database</secondary> + </indexterm> + <indexterm> + <primary>Database</primary> + <secondary>System Requirements</secondary> + </indexterm> + <table> + <title>Supported Database and JDBC driver Combinations</title> + <tgroup cols="2"> + <colspec colnum="1" colname="c1" colwidth="1*"></colspec> + <colspec colnum="2" colname="c2" colwidth="1*"></colspec> <spanspec spanname="hspan" namest="c1" nameend="c2" align="left"></spanspec> - <thead> - <row> - <entry> - <emphasis>Database</emphasis> - </entry> - <entry> - <emphasis>Database driver</emphasis> - </entry> - </row> - </thead> - <tbody> + <thead> + <row> + <entry> + <emphasis>Database</emphasis> + </entry> + <entry> + <emphasis>Database driver</emphasis> + </entry> + </row> + </thead> + <tbody> <row> - <entry spanname="hspan"> + <entry spanname="hspan"> <emphasis><emphasis role="bold">JBoss Enterprise Portal Platform 5.0</emphasis></emphasis> - </entry> + </entry> </row> - <row> - <entry> - MySQL 5.1 - </entry> - <entry> - MySQL Connector/J 5.1.8 - </entry> - </row> - <row> - <entry> + <row> + <entry> + MySQL 5.1 + </entry> + <entry> + MySQL Connector/J 5.1.8 + </entry> + </row> + <row> + <entry> Oracle 10g R2  - </entry> - <entry> + </entry> + <entry> 10g R2  - </entry> - </row> - <row> - <entry> + </entry> + </row> + <row> + <entry> Oracle 11g R1 (Supported) - </entry> - <entry> + </entry> + <entry> 11g R1  - </entry> - </row> - <row> - <entry> + </entry> + </row> + <row> + <entry> Oracle 11g RAC  (Supported) - </entry> - <entry> + </entry> + <entry> 11g R1  - </entry> - </row> - <row> - <entry> - Microsoft SQL Server 2005 SP3 - </entry> - <entry> - Microsoft JDBC Driver 2.0 - </entry> - </row> - <row> - <entry> - Microsoft SQL Server 2008 SP1 - </entry> - <entry> - Microsoft JDBC Driver 2.0 - </entry> - </row> - <row> - <entry> - PostgresSQL 8.3.7 - </entry> - <entry> - PostgresSQL Driver JDBC4, 8.3-605 - </entry> - </row> - <row> - <entry> - PostgresSQL 8.2.4 (Supported) - </entry> - <entry> - PostgresSQL Driver JDBC4, 8.2-510 - </entry> - </row> - <row> - <entry> - DB2 9.7 - </entry> - <entry> - IBM Data Server Driver for JDBC and SQLJ (JCC Driver) Version: 9.1 (fixpack 3a) - </entry> - </row> - <row> - <entry> - Sybase 15.0.2 - </entry> - <entry> + </entry> + </row> + <row> + <entry> + Microsoft SQL Server 2005 SP3 + </entry> + <entry> + Microsoft JDBC Driver 2.0 + </entry> + </row> + <row> + <entry> + Microsoft SQL Server 2008 SP1 + </entry> + <entry> + Microsoft JDBC Driver 2.0 + </entry> + </row> + <row> + <entry> + PostgresSQL 8.3.7 + </entry> + <entry> + PostgresSQL Driver JDBC4, 8.3-605 + </entry> + </row> + <row> + <entry> + PostgresSQL 8.2.4 (Supported) + </entry> + <entry> + PostgresSQL Driver JDBC4, 8.2-510 + </entry> + </row> + <row> + <entry> + DB2 9.7 + </entry> + <entry> + IBM Data Server Driver for JDBC and SQLJ (JCC Driver) Version: 9.1 (fixpack 3a) + </entry> + </row> + <row> + <entry> + Sybase 15.0.2 + </entry> + <entry> JConnect v6.0.5  - </entry> - </row> + </entry> + </row> <row> - <entry spanname="hspan"> + <entry spanname="hspan"> <emphasis><emphasis role="bold">JBoss Enterprise Portal Platform 5.1</emphasis></emphasis> - </entry> + </entry> </row> <row> - <entry> - Oracle 11g R2 - </entry> - <entry> - 11g R2 - </entry> - </row> - <row> - <entry> - Oracle 11g R2 RAC - </entry> - <entry> - 11g R2 RAC - </entry> - </row> - </tbody> - </tgroup> - </table> + <entry> + Oracle 11g R2 + </entry> + <entry> + 11g R2 + </entry> + </row> + <row> + <entry> + Oracle 11g R2 RAC + </entry> + <entry> + 11g R2 RAC + </entry> + </row> + </tbody> + </tgroup> + </table> - <indexterm> - <primary>System Requirements</primary> - <secondary>Directory server</secondary> - </indexterm> - <para> - The following is a list of supported directory servers: - </para> - - <table> - <title>Supported and Certified directory servers</title> - <tgroup cols="2"> - <colspec colnum="1" colname="LDAP" colwidth="1*"></colspec> - <thead> - <row> - <entry> - <emphasis>Directory Server</emphasis> - </entry> + <indexterm> + <primary>System Requirements</primary> + <secondary>Directory server</secondary> + </indexterm> + <para> + The following is a list of supported directory servers: + </para> + + <table> + <title>Supported and Certified directory servers</title> + <tgroup cols="2"> + <colspec colnum="1" colname="LDAP" colwidth="1*"></colspec> + <thead> + <row> + <entry> + <emphasis>Directory Server</emphasis> + </entry> <entry> <emphasis>Version</emphasis> </entry> - </row> - </thead> - <tbody> - <row> - <entry> - OpenDS - </entry> + </row> + </thead> + <tbody> + <row> + <entry> + OpenDS + </entry> <entry> 1.2 </entry> - </row> - <row> - <entry> - OpenDS - </entry> + </row> + <row> + <entry> + OpenDS + </entry> <entry> 2.0 </entry> - </row> - <row> - <entry> - OpenLDAP - </entry> + </row> + <row> + <entry> + OpenLDAP + </entry> <entry> 2.4 </entry> - </row> - <row> - <entry> - Red Hat Directory Server - </entry> + </row> + <row> + <entry> + Red Hat Directory Server + </entry> <entry> 7.1 </entry> - </row> - <row> - <entry> - MS Active Directory - </entry> + </row> + <row> + <entry> + MS Active Directory + </entry> <entry> Windows Server 2008 </entry> - </row> - </tbody> - </tgroup> - </table> + </row> + </tbody> + </tgroup> + </table>  - </section> - - <section id="Pre_Requisites-Configuring_Your_Java_Environment"> - <title>Configuring Your Java Environment</title> - - <para> - You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss Enterprise Portal Platform. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 6.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM. - </para> - - <itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware"> - <title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title> - <listitem> - <para> - Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications. - </para> - </listitem> - <listitem> - <para> - 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection. - </para> - </listitem> - <listitem> - <para> - Applications that run with more than 1.5 GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM. - </para> - </listitem> - </itemizedlist> - <note> - <para> - Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin. - </para> - </note> - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_using_RHN"> - <title>Installing and Configuring JDK 6.0 using RHN</title> - <listitem> - <para> - Java SDKs are provided by the Red Hat Enterprise Linux 5 Base and Supplementary channels for your Linux variant and architecture. The available JDKs corresponding to each channel and architecture are listed below: - </para> - <variablelist> - <title>Red Hat Enterprise Linux 5 Java SDKs</title> + </section> + + <section id="Pre_Requisites-Configuring_Your_Java_Environment"> + <title>Configuring Your Java Environment</title> + + <para> + You must have a working installation of <emphasis role="bold">JDK 1.6</emphasis> before you install JBoss Enterprise Portal Platform. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 6.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM. + </para> + + <itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware"> + <title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title> + <listitem> + <para> + Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications. + </para> + </listitem> + <listitem> + <para> + 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection. + </para> + </listitem> + <listitem> + <para> + Applications that run with more than 1.5 GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM. + </para> + </listitem> + </itemizedlist> + <note> + <para> + Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin. + </para> + </note> + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_using_RHN"> + <title>Installing and Configuring JDK 6.0 using RHN</title> + <listitem> + <para> + Java SDKs are provided by the Red Hat Enterprise Linux 5 Base and Supplementary channels for your Linux variant and architecture. The available JDKs corresponding to each channel and architecture are listed below: + </para> + <variablelist> + <title>Red Hat Enterprise Linux 5 Java SDKs</title> <varlistentry> <term> Channel: rhel-<arch>-server-5 </term> <listitem> <para> - java-1.6.0-openjdk + java-1.6.0-openjdk </para> </listitem> </varlistentry> @@ -515,11 +531,11 @@ </term> <listitem> <para> - java-1.6.0-sun (Sun) + java-1.6.0-sun (Sun) </para> <para> - java-1.6.0-ibm (IBM) + java-1.6.0-ibm (IBM) </para> </listitem> </varlistentry> @@ -527,113 +543,113 @@ <para> Ensure that the -devel packages are also installed. </para> - </listitem> - - <listitem> - <para> - Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional). - </para> - - <para> - This is only needed if you want to use the SysV service script - and/or want this installed SDK to be the default java and javac - in the system. This choice can often be overridden by setting - the <command moreinfo="none">JAVA_HOME</command> environment variable. - </para> - - <para> - The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources, to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want. - </para> - - <para> - As root, issue the following command: - </para> - <screen><command moreinfo="none">/usr/sbin/alternatives --config java</command></screen> - <para> - and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. - </para> - - <para> - Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version. - </para> - </listitem> - </itemizedlist> - - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_a_generic_Linux_platform"> - <title>Installing and Configuring JDK 6.0 on a generic Linux platform</title> - <listitem> - <para> - Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need"></ulink>. - </para> - </listitem> - <listitem> - <para> - From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp"></ulink>. - </para> - </listitem> - <listitem> - <para> - Follow the instructions presented on this page including selecting the appropriate platform and architecture. - </para> - </listitem> - <listitem> - <para> - Clicking the <guibutton>Continue</guibutton> button will display the download options (depending on whether the user chooses to register): - </para> - <itemizedlist> - <listitem> - <para> - jdk-6u<update number>-linux-<arch>-rpm.bin or; - </para> - </listitem> - <listitem> - <para> - jdk-6u<update number>-linux-<arch>.bin - </para> - </listitem> - </itemizedlist> - <para>If installing the JDK on Red Hat Enterprise Linux, Fedora, or another RPM-based Linux system, it is recommended that the self-extracting file containing the RPM package is selected. This option will set up and use the SysV service scripts in addition to installing the JDK. The RPM option is also recommended if the JBoss Enterprise Portal Platform is being set up in a production environment. - </para> - </listitem> - - <listitem> - <para> - Create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. <programlisting> + </listitem> + + <listitem> + <para> + Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0</command> (setting <command moreinfo="none">java_sdk_1.6.0</command> is optional). + </para> + + <para> + This is only needed if you want to use the SysV service script + and/or want this installed SDK to be the default java and javac + in the system. This choice can often be overridden by setting + the <command moreinfo="none">JAVA_HOME</command> environment variable. + </para> + + <para> + The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources, to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want. + </para> + + <para> + As root, issue the following command: + </para> + <screen><command moreinfo="none">/usr/sbin/alternatives --config java</command></screen> + <para> + and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. + </para> + + <para> + Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.6.0.</command> We recommend that all point to the same manufacturer and version. + </para> + </listitem> + </itemizedlist> + + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_a_generic_Linux_platform"> + <title>Installing and Configuring JDK 6.0 on a generic Linux platform</title> + <listitem> + <para> + Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need"></ulink>. + </para> + </listitem> + <listitem> + <para> + From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp"></ulink>. + </para> + </listitem> + <listitem> + <para> + Follow the instructions presented on this page including selecting the appropriate platform and architecture. + </para> + </listitem> + <listitem> + <para> + Clicking the <guibutton>Continue</guibutton> button will display the download options (depending on whether the user chooses to register): + </para> + <itemizedlist> + <listitem> + <para> + jdk-6u<update number>-linux-<arch>-rpm.bin or; + </para> + </listitem> + <listitem> + <para> + jdk-6u<update number>-linux-<arch>.bin + </para> + </listitem> + </itemizedlist> + <para>If installing the JDK on Red Hat Enterprise Linux, Fedora, or another RPM-based Linux system, it is recommended that the self-extracting file containing the RPM package is selected. This option will set up and use the SysV service scripts in addition to installing the JDK. The RPM option is also recommended if the JBoss Enterprise Portal Platform is being set up in a production environment. + </para> + </listitem> + + <listitem> + <para> + Create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. <programlisting> #In this example /usr/java/jdk1.6.0_19 is the JDK installation directory. export JAVA_HOME=/usr/java/jdk1.6.0_19 export PATH=$PATH:$JAVA_HOME/bin </programlisting> - Set this variable for the user account performing the installation and also for the user account that will run the server. - </para> - </listitem> - <listitem> - <para> - If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system. - <note> - <para> - Selecting alternatives as decribed below can be avoided by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. - </para> - </note> - <itemizedlist> - <title>Select alternatives for java, javac and java_sdk_1.6.0</title> - - <listitem> - <para> - As root, type the following command at the shell prompt and you should see something like this: - </para> + Set this variable for the user account performing the installation and also for the user account that will run the server. + </para> + </listitem> + <listitem> + <para> + If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.6 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system. + <note> + <para> + Selecting alternatives as decribed below can be avoided by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step. + </para> + </note> + <itemizedlist> + <title>Select alternatives for java, javac and java_sdk_1.6.0</title> + + <listitem> + <para> + As root, type the following command at the shell prompt and you should see something like this: + </para> <programlisting>[root@vsr ~]$ /usr/sbin/alternatives --config java There are 2 programs which provide 'java'. Selection Command @@ -644,17 +660,17 @@ </programlisting> <para> - Make sure the Sun version - <literal>jre-1.6.0-sun</literal> in this case - is selected (marked with a '+' in the output), or select it by entering its number as prompted. - </para> - </listitem> - <listitem> - <para> - Repeat the same for javac and java_sdk_1.6.0. - </para> - <programlisting> + Make sure the Sun version - <literal>jre-1.6.0-sun</literal> in this case - is selected (marked with a '+' in the output), or select it by entering its number as prompted. + </para> + </listitem> + <listitem> + <para> + Repeat the same for javac and java_sdk_1.6.0. + </para> + <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config javac There are 1 programs which provide 'javac'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.6.0-sun/bin/javac Enter to keep the current selection[+], or type selection number: @@ -662,84 +678,84 @@ <programlisting> [root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.6.0 There are 1 programs which provide 'java_sdk_1.6.0'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.6.0-sun Enter to keep the current selection[+], or type selection number: </programlisting> <para> You should verify that java, javac and java_sdk_1.6.0 all point to the same manufacturer and version. - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para> - Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this: <programlisting> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + <listitem> + <para> + Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this: <programlisting> [root@vsr ~]$ java -version java version "1.6.0_19" Java(TM) SE Runtime Environment (build 1.6.0_19-b01) Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode) </programlisting> - </para> - </listitem> - </itemizedlist> - - <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_Microsoft_Windows"> - <title>Installing and Configuring JDK 6.0 on Microsoft Windows</title> - <listitem> - <para> - Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp#need"></ulink>. - </para> - </listitem> - <listitem> - <para> - From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://java.sun.com/javase/downloads/widget/jdk6.jsp"></ulink>. - </para> - </listitem> - <listitem> - <para> - Follow the instructions presented on this page including selecting the appropriate platform and architecture. - </para> - </listitem> - <listitem> - <para> - Clicking the <guibutton>Continue</guibutton> button will display the download option (depending on whether the user chooses to register): - </para> - <itemizedlist> - <listitem> - <para> - jdk-6u<update number>-windows-<arch>.exe - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para> - Create an environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\</literal>. - </para> - </listitem> - <listitem> - <para> - In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\jre\bin</literal>. You may set these variables by going to the System Properties window then select the Advanced tab and finally click on the Environment Variables button. - </para> - </listitem> - </itemizedlist> - </section> + </para> + </listitem> + </itemizedlist> + + <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_JDK_6.0_on_Microsoft_Windows"> + <title>Installing and Configuring JDK 6.0 on Microsoft Windows</title> + <listitem> + <para> + Download the Java 2 Platform, Standard Edition (J2SE) Development Kit (JDK) 6.0 from Oracle's website: <ulink type="http" url="http://www.oracle.com/technetwork/java/javase/downloads/index.html#need"></ulink>. + </para> + </listitem> + <listitem> + <para> + From this page, select the latest update under the <literal>Java Platform, Standard Edition</literal> heading. Alternatively, this page can be accessed directly at <ulink url="http://www.oracle.com/technetwork/java/javase/downloads/jdk6-jsp-136632.html"></ulink>. + </para> + </listitem> + <listitem> + <para> + Follow the instructions presented on this page including selecting the appropriate platform and architecture. + </para> + </listitem> + <listitem> + <para> + Clicking the <guibutton>Continue</guibutton> button will display the download option (depending on whether the user chooses to register): + </para> + <itemizedlist> + <listitem> + <para> + jdk-6u<update number>-windows-<arch>.exe + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + Create an environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\</literal>. + </para> + </listitem> + <listitem> + <para> + In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Program Files\Java\jdk1.6.0_19\jre\bin</literal>. You may set these variables by going to the System Properties window then select the Advanced tab and finally click on the Environment Variables button. + </para> + </listitem> + </itemizedlist> + </section> - </section> + </section> <section> - <title>Recommended Practices</title> - <para> - JBoss Enterprise Portal Platform includes four pre-configured user accounts for testing and evaluation purposes. These accounts can be used for direct access to the portal. - </para> - <para> - For security reasons, before going in production, you should restrict the access to the login servlet to POST. - </para> - <para> + <title>Recommended Practices</title> + <para> + JBoss Enterprise Portal Platform includes four pre-configured user accounts for testing and evaluation purposes. These accounts can be used for direct access to the portal. + </para> + <para> + For security reasons, before going in production, you should restrict the access to the login servlet to POST. + </para> + <para> To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: - </para> + </para> <programlisting language="XML" role="XML"><![CDATA[ <security-constraint> <web-resource-collection> @@ -754,10 +770,10 @@ </web-resource-collection> <auth-constraint/> </security-constraint> ]]></programlisting> - <para> - Doing this will render the login links provided on the front page inactive. - </para> - - </section> + <para> + Doing this will render the login links provided on the front page inactive. + </para> + + </section> </chapter> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -226,7 +226,7 @@ <formalpara> <title>Disabling Authentication for JMX Invoker:</title> <para> - To disable authentication for the JMX invoker, edit the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/jmx-invoker-service.xml</filename> file to comment out the security interceptor passthrough: + To disable authentication for the JMX invoker, edit the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jmx-invoker-service.xml</filename> file to comment out the security interceptor passthrough: </para> </formalpara> <para> @@ -255,7 +255,7 @@ For security reasons, before going in production, you should restrict the access to the login servlet to POST. </para> <para> - To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: + To do so, edit the file <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add: </para> <programlisting language="XML" role="XML"><![CDATA[ <security-constraint> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -9,6 +9,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-4</revnumber> + <date>Tue Dec 13 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>JBEPP-1431: Actioning QA feedback.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-3</revnumber> <date>Tue Nov 15 2011</date> <author> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2011-12-13 06:54:33 UTC (rev 8242) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2011-12-13 07:25:12 UTC (rev 8243) @@ -5,100 +5,97 @@ ]> <chapter id="Test_your_Installation"> - <title>Test your Installation</title> + <title>Test your Installation</title> - <para> - After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple start up test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> environment variables as explained in <xref linkend="Post_Installation_Configuration"/>. - </para> - <para> - To test your installation: - <itemizedlist> - <listitem> - <para> + <para> + After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple start up test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> environment variables as explained in <xref linkend="Post_Installation_Configuration"/>. + </para> + <para> + To test your installation: + <itemizedlist> + <listitem> + <para> move to the <filename><replaceable>JBOSS_HOME</replaceable>/bin</filename> directory; - </para> - </listitem> - <listitem> - <para> - execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system; - <itemizedlist> - <listitem> - <para> + </para> + </listitem> + <listitem> + <para> + execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system; + <itemizedlist> + <listitem> + <para> Ensure that you run the configuration corresponding to the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/</filename> chosen in <xref linkend="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database"></xref> - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - </itemizedlist> - </para> - <para> - The example below uses the production configuration. Your output should look like the following (accounting for installation directory differences and version numbers) and should not contain any error or exception messages: - </para> + </para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + </para> + <para> + The example below uses the production configuration. Your output should look like the following (accounting for installation directory differences and version numbers) and should not contain any error or exception messages: + </para> <programlisting> [user@localhost bin]$ ./run.sh -c production ========================================================================= JBoss Bootstrap Environment - JBOSS_HOME: /home/user/jboss-epp-5.0/jboss-as + JBOSS_HOME: /var/jboss-epp/jboss-as - JAVA: /usr/java/jdk1.6.0_16/bin/java + JAVA: java - JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m - -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 - -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true - -Dexo.conf.dir.name=gatein -Djava.net.preferIPv4Stack=true + JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true - CLASSPATH: /home/user/jboss-epp-5.0/jboss-as/bin/run.jar/usr/java/jdk1.6.0_16/lib/tools.jar + CLASSPATH: /var/jboss-epp/jboss-as/bin/run.jar ========================================================================= -16:59:41,401 INFO [ServerImpl] Starting JBoss (Microcontainer)... -16:59:41,401 INFO [ServerImpl] Release ID: JBoss [EAP] 5.0.0.GA (build: SVNTag=JBPAPP_5_0_0_GA date=200910202128) -16:59:41,402 INFO [ServerImpl] Bootstrap URL: null -16:59:41,402 INFO [ServerImpl] Home Dir: /home/user/jboss-epp-5.0/jboss-as -16:59:41,402 INFO [ServerImpl] Home URL: file:/home/user/jboss-epp-5.0/jboss-as/ -16:59:41,402 INFO [ServerImpl] Library URL: file:/home/user/jboss-epp-5.0/jboss-as/lib/ -16:59:41,403 INFO [ServerImpl] Patch URL: null -16:59:41,403 INFO [ServerImpl] Common Base URL: file:/home/user/jboss-epp-5.0/jboss-as/common/ -16:59:41,404 INFO [ServerImpl] Common Library URL: file:/home/user/jboss-epp-5.0/jboss-as/common/lib/ -16:59:41,404 INFO [ServerImpl] Server Name: production +23:27:30,376 INFO [ServerImpl] Starting JBoss (Microcontainer)... +23:27:30,376 INFO [ServerImpl] Release ID: JBoss [EPP] JBoss-EPP 5.2.0.GA (build: SVNTag=5.2.0.GA date=201112080623) +23:27:30,376 INFO [ServerImpl] Bootstrap URL: null +23:27:30,377 INFO [ServerImpl] Home Dir: /var/jboss-epp/jboss-as +23:27:30,377 INFO [ServerImpl] Home URL: file:/var/jboss-epp/jboss-as/ +23:27:30,377 INFO [ServerImpl] Library URL: file:/var/jboss-epp/jboss-as/lib/ +23:27:30,377 INFO [ServerImpl] Patch URL: null +23:27:30,377 INFO [ServerImpl] Common Base URL: file:/var/jboss-epp/jboss-as/common/ +23:27:30,377 INFO [ServerImpl] Common Library URL: file:/var/jboss-epp/jboss-as/common/lib/ +23:27:30,377 INFO [ServerImpl] Server Name: default ... ... -16:59:44,345 INFO [JMXKernel] Legacy JMX core initialized +23:27:32,061 INFO [JMXKernel] Legacy JMX core initialized </programlisting> - <note><title>Note: Production server log file</title> - <para> - There is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename><replaceable>JBOSS_HOME</replaceable>/server/production/log</filename> subdirectory. - </para> - </note> + <note><title>Note: Production server log file</title> + <para> + There is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename><replaceable>JBOSS_HOME</replaceable>/server/production/log</filename> subdirectory. + </para> + </note> - <para> - Ensure that port 8080 is not already in use and open <literal>http://localhost:8080/portal</literal> in your web browser. - <note> - <para> + <para> + Ensure that port 8080 is not already in use and open <literal>http://localhost:8080/portal</literal> in your web browser. + <note> + <para> On some machines, the name localhost won’t resolve properly and you should use the local loopback address <ulink type="http" url="127.0.0.1">127.0.0.1</ulink> instead. - </para> - </note> - The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />. - </para> - <para> - <figure id="Test_your_Installation-Test_your_Installation"> - <title>Test your Installation</title> - <mediaobject> - <imageobject role="html"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100" /> - </imageobject> - <imageobject role="fo"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px" /> - </imageobject> - </mediaobject> - </figure> - </para> - <para> - You are now ready to use JBoss Enterprise Portal Platform. Refer to the User Guide and Reference Guide for more information about the product's feature set and example applications showcasing JBoss Enterprise Portal Platform in action. - </para> - + </para> + </note> + The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />. + </para> + <para> + <figure id="Test_your_Installation-Test_your_Installation"> + <title>Test your Installation</title> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px" /> + </imageobject> + </mediaobject> + </figure> + </para> + <para> + You are now ready to use JBoss Enterprise Portal Platform. Refer to the User Guide and Reference Guide for more information about the product's feature set and example applications showcasing JBoss Enterprise Portal Platform in action. + </para> + </chapter>

13 years

1
0
0 / 0

gatein SVN: r8242 - in epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US: images and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-13 01:54:33 -0500 (Tue, 13 Dec 2011) New Revision: 8242 Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/defaultaccess.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/highlight_category.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/more_drop_menu.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/print_bar.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/shared_user_space.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/templateform.png Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml Log: JBEPP-1437: Actioning QA feedback Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml 2011-12-13 06:48:07 UTC (rev 8241) +++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml 2011-12-13 06:54:33 UTC (rev 8242) @@ -7,21 +7,21 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>5.2.0-7</revnumber> + <date>Tue Dec 13 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>JBEPP-1437/JBEPP-1135: Actioning QA feedback.</member> + </simplelist> + </revdescription> + </revision> <revision> - <revision> - <revnumber>5.2.0-6</revnumber> - <date>Tue Dec 13 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - </author> - <revdescription> - <simplelist> - <member>JBEPP-1437: Actioning QA feedback.</member> - </simplelist> - </revdescription> - </revision> <revnumber>5.2.0-4</revnumber> <date>Thu Dec 1 2011</date> <author> Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/defaultaccess.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/defaultaccess.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/highlight_category.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/highlight_category.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/more_drop_menu.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/more_drop_menu.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/print_bar.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/print_bar.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/shared_user_space.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/shared_user_space.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/templateform.png =================================================================== (Binary files differ) Property changes on: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/templateform.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream

13 years

1
0
0 / 0

gatein SVN: r8241 - epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-13 01:48:07 -0500 (Tue, 13 Dec 2011) New Revision: 8241 Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Newsletters.xml Log: JBEPP-1135: Actioning QA feedback Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Newsletters.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Newsletters.xml 2011-12-13 06:47:03 UTC (rev 8240) +++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Newsletters.xml 2011-12-13 06:48:07 UTC (rev 8241) @@ -353,6 +353,9 @@ <imageobject> <imagedata fileref="images/newsletters_ban_icon.png" format="PNG" width="8mm"/> </imageobject> + <textobject> + <phrase>Page with closed lock icon</phrase> + </textobject> </inlinemediaobject> </entry> <entry> To ban this user from receiving email. </entry> @@ -363,6 +366,9 @@ <imageobject> <imagedata fileref="images/newsletters_unban_icon.png" format="PNG" width="7mm"/> </imageobject> + <textobject> + <phrase>Page with closed lock icon</phrase> + </textobject> </inlinemediaobject> </entry> <entry> To remove a ban on a user. </entry> @@ -373,6 +379,9 @@ <imageobject> <imagedata fileref="images/trashicon.png" format="PNG" width="5mm"/> </imageobject> + <textobject> + <phrase></phrase> + </textobject> </inlinemediaobject> </entry> <entry> To delete the user. </entry>

13 years

1
0
0 / 0

gatein SVN: r8240 - in epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US: modules/Basics and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-13 01:47:03 -0500 (Tue, 13 Dec 2011) New Revision: 8240 Removed: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/newsletters_ban_icon.png epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/newsletters_unban_icon.png Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Contribute_Content.xml epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Search.xml Log: JBEPP-1135: Actioning QA feedback Deleted: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/newsletters_ban_icon.png =================================================================== (Binary files differ) Deleted: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/images/newsletters_unban_icon.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Contribute_Content.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Contribute_Content.xml 2011-12-13 06:35:25 UTC (rev 8239) +++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Contribute_Content.xml 2011-12-13 06:47:03 UTC (rev 8240) @@ -77,7 +77,7 @@ </para> <para> - For Single Content Viewer (SCV), you can see the current state of the content, the <guilabel>Edit Content</guilabel> icon and <guilabel>References</guilabel> icon. + For Single Content Viewer (SCV), you can see the current state of the content, the <guilabel>Edit Content</guilabel> icon and <guilabel>Preferences</guilabel> icon. </para> <mediaobject> @@ -91,7 +91,7 @@ </mediaobject> <para> - For <systemitem>Content List Viewer</systemitem> (CLV), you can see the current state of the content, the <guilabel>Edit Content</guilabel>, <guilabel>References</guilabel> icon, the <guilabel>Add Content</guilabel> icon and the <guilabel>Management Content</guilabel> icon. + For <systemitem>Content List Viewer</systemitem> (CLV), you can see the current state of the content, the <guilabel>Edit Content</guilabel>, <guilabel>Preferences</guilabel> icon, the <guilabel>Add Content</guilabel> icon and the <guilabel>Management Content</guilabel> icon. </para> <mediaobject> Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Search.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Search.xml 2011-12-13 06:35:25 UTC (rev 8239) +++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/modules/Basics/Search.xml 2011-12-13 06:47:03 UTC (rev 8240) @@ -304,21 +304,13 @@ </row> <row> <entry> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/addnodetypeicon.png" format="PNG" width="9mm"/> - </imageobject> - </inlinemediaobject> + 6 </entry> <entry> Add a document type. </entry> </row> <row> <entry> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/addcategoryicon.png" format="PNG" width="6mm"/> - </imageobject> - </inlinemediaobject> + 7 </entry> <entry> Add a category. </entry> </row>

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits December 2011