May 2010 - gatein-commits - Jboss List Archives

gatein SVN: r3127 - portal/trunk/server/tomcat/patch/src/main/tomcat.

by do-not-reply＠jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-05-19 09:55:10 -0400 (Wed, 19 May 2010) New Revision: 3127 Modified: portal/trunk/server/tomcat/patch/src/main/tomcat/GATEIN-README.txt Log: Minor fixes Modified: portal/trunk/server/tomcat/patch/src/main/tomcat/GATEIN-README.txt =================================================================== --- portal/trunk/server/tomcat/patch/src/main/tomcat/GATEIN-README.txt 2010-05-19 12:24:37 UTC (rev 3126) +++ portal/trunk/server/tomcat/patch/src/main/tomcat/GATEIN-README.txt 2010-05-19 13:55:10 UTC (rev 3127) @@ -23,12 +23,12 @@ * On the Windows platform Open a DOS prompt command, go to tomcat/bin and type the command "gatein.bat run" for production - "gatein.bat run" for development + "gatein-dev.bat run" for development * On Unix/linux/cygwin/MacOSX Open a terminal, go to tomcat/bin and type the command: "./gatein.sh run" for production - "./gatein.sh run" for development + "./gatein-dev.sh run" for development You may need to change the permission of all *.sh files in the tomcat/bin dir by using: chmod +x *.sh @@ -47,4 +47,4 @@ For more documentation and latest updated news, please visit our website www.gatein.org. Thank your for using GateIn ! -JBoss & eXo Platform develoment teams +JBoss & eXo Platform development teams

14 years, 1 month

1
0
0 / 0

gatein SVN: r3126 - portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR.

by do-not-reply＠jboss.org

Author: smumford Date: 2010-05-19 08:24:37 -0400 (Wed, 19 May 2010) New Revision: 3126 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml Log: Minor edit to section 17.11.1 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-05-19 12:18:28 UTC (rev 3125) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-05-19 12:24:37 UTC (rev 3126) @@ -140,40 +140,39 @@ </programlistingco> <formalpara> - <title>JBoss-Cache template configuration</title> + <title>JBoss Cache template configuration</title> <para> - JBoss-Cache template configuration for query handler. + Below is an example JBoss Cache template configuration file for the query handler (<filename>jbosscache-indexer.xml</filename>). </para> </formalpara> - <para> - jbosscache-indexer.xml -<programlisting><?xml version="1.0" encoding="UTF-8"?> -<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> + +<programlisting language="XML" role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> +<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> - <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" - lockAcquisitionTimeout="20000" /> -  - <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup" /> + <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" + lockAcquisitionTimeout="20000" /> +  + <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup" /> - <clustering mode="replication" clusterName="${jbosscache-cluster-name}"> - <stateRetrieval timeout="20000" fetchInMemoryState="false" /> - <jgroupsConfig multiplexerStack="jcr.stack" /> - <sync /> - </clustering> -  - <eviction wakeUpInterval="5000"> - <default algorithmClass="org.jboss.cache.eviction.FIFOAlgorithm" eventQueueSize="1000000"> - <property name="maxNodes" value="10000" /> - <property name="minTimeToLive" value="60000" /> - </default> - </eviction> + <clustering mode="replication" clusterName="${jbosscache-cluster-name}"> + <stateRetrieval timeout="20000" fetchInMemoryState="false" /> + <jgroupsConfig multiplexerStack="jcr.stack" /> + <sync /> + </clustering> +  + <eviction wakeUpInterval="5000"> + <default algorithmClass="org.jboss.cache.eviction.FIFOAlgorithm" eventQueueSize="1000000"> + <property name="maxNodes" value="10000" /> + <property name="minTimeToLive" value="60000" /> + </default> + </eviction> -</jbosscache> -</programlisting> - </para> +</jbosscache>]]></programlisting> + + </section>

14 years, 1 month

1
0
0 / 0

gatein SVN: r3125 - portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2010-05-19 08:18:28 -0400 (Wed, 19 May 2010) New Revision: 3125 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml Log: Fixed copy&paste error. Lots of other spots need to be fixed due to mass replace of we -> the WSRP component that didn't make sense in lots of spots. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml 2010-05-19 08:33:11 UTC (rev 3124) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/WSRP.xml 2010-05-19 12:18:28 UTC (rev 3125) @@ -32,9 +32,7 @@ More information on WSRP can be found on the official <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">website</ulink>. </para> <para> - The <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html, not http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp - ----------------- -">primer</ulink> is suggested reading for a comprehensive overview of WSRP. + The <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> is suggested reading for a comprehensive overview of WSRP. </para> </section>

14 years, 1 month

1
0
0 / 0

gatein SVN: r3124 - portal/trunk/portlet/exoadmin/src/main/java/org/exoplatform/navigation/webui/component.

by do-not-reply＠jboss.org

Author: hoang_to Date: 2010-05-19 04:33:11 -0400 (Wed, 19 May 2010) New Revision: 3124 Modified: portal/trunk/portlet/exoadmin/src/main/java/org/exoplatform/navigation/webui/component/UISiteManagement.java Log: Rollback the Javacode on navigation edit permission check. For release 3.1, the former check on PortalConfig is reused. That should be modified right after Modified: portal/trunk/portlet/exoadmin/src/main/java/org/exoplatform/navigation/webui/component/UISiteManagement.java =================================================================== --- portal/trunk/portlet/exoadmin/src/main/java/org/exoplatform/navigation/webui/component/UISiteManagement.java 2010-05-19 07:47:45 UTC (rev 3123) +++ portal/trunk/portlet/exoadmin/src/main/java/org/exoplatform/navigation/webui/component/UISiteManagement.java 2010-05-19 08:33:11 UTC (rev 3124) @@ -336,8 +336,30 @@ DataStorage dataService = uicomp.getApplicationComponent(DataStorage.class); WebuiRequestContext context = event.getRequestContext(); UIApplication uiApplication = context.getUIApplication(); - + + //Minh Hoang TO: User could edit navigation if he/she has edit permissions on PortalConfig. That is not + //at all logical and should be modified after release 3.1 GA + UserPortalConfigService configService = uicomp.getApplicationComponent(UserPortalConfigService.class); + UserPortalConfig userPortalConfig = configService.getUserPortalConfig(portalName, context.getRemoteUser()); + if(userPortalConfig == null) + { + uiApplication.addMessage(new ApplicationMessage("UISiteManagement.msg.portal-not-exist", + new String[]{portalName})); + return; + } + + UserACL userACL = uicomp.getApplicationComponent(UserACL.class); + if (!userACL.hasEditPermission(userPortalConfig.getPortalConfig())) + { + uiApplication.addMessage(new ApplicationMessage("UISiteManagement.msg.Invalid-editPermission", null));; + return; + } + PageNavigation edittedNavigation = dataService.getPageNavigation(PortalConfig.PORTAL_TYPE, portalName); + + + //Minh Hoang TO: For release 3.1, Edit Permission check would be rollback to former checks on PortalConfig + /* if (edittedNavigation == null) { uiApplication.addMessage(new ApplicationMessage("UISiteManagement.msg.portal-not-exist", @@ -351,7 +373,8 @@ uiApplication.addMessage(new ApplicationMessage("UISiteManagement.msg.Invalid-editPermission", null));; return; } - + */ + UIPopupWindow popUp = uicomp.getChild(UIPopupWindow.class); UINavigationManagement naviManager = popUp.createUIComponent(UINavigationManagement.class, null, null, popUp); naviManager.setOwner(portalName);

14 years, 1 month

1
0
0 / 0

gatein SVN: r3123 - portal/trunk/web/eXoResources/src/main/webapp/skin/DefaultSkin/portal/webui/component/view/UIPortalComponent.

by do-not-reply＠jboss.org

Author: thanh.do Date: 2010-05-19 03:47:45 -0400 (Wed, 19 May 2010) New Revision: 3123 Modified: portal/trunk/web/eXoResources/src/main/webapp/skin/DefaultSkin/portal/webui/component/view/UIPortalComponent/Stylesheet.css Log: GTNPORTAL-1045:Can't drag & drop application into container when click switch view mode Modified: portal/trunk/web/eXoResources/src/main/webapp/skin/DefaultSkin/portal/webui/component/view/UIPortalComponent/Stylesheet.css =================================================================== --- portal/trunk/web/eXoResources/src/main/webapp/skin/DefaultSkin/portal/webui/component/view/UIPortalComponent/Stylesheet.css 2010-05-19 07:47:16 UTC (rev 3122) +++ portal/trunk/web/eXoResources/src/main/webapp/skin/DefaultSkin/portal/webui/component/view/UIPortalComponent/Stylesheet.css 2010-05-19 07:47:45 UTC (rev 3123) @@ -138,8 +138,8 @@ _height: 86px; } -.UIContainer .VIEW-BLOCK .UIRowContainer { - min-height: 20px; +.UIContainer .VIEW-BLOCK .EmptyContainer { + height: 82px; } .UIContainer .NewLayer {

14 years, 1 month

1
0
0 / 0

gatein SVN: r3122 - portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR.

by do-not-reply＠jboss.org

Author: smumford Date: 2010-05-19 03:47:16 -0400 (Wed, 19 May 2010) New Revision: 3122 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml Log: JBEPP-276: Continuing edits to JCR section. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2010-05-19 07:37:40 UTC (rev 3121) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2010-05-19 07:47:16 UTC (rev 3122) @@ -7,175 +7,216 @@ <title>LockManager</title> <para> - In common words, LockManager stores lock objects, so it can give Lock object or can release it, etc. + The LockManager stores lock objects. It can lock or release objects as required. It is also responsible for removing stale locks. </para> <para> - Also LockManager is responsible for removing Locks that live too long. This parameter may be configured with "time-out" property. + The length of time LockManager allows a lock to remain in place can be configured with the "<literal>time-out</literal>" property. </para> <para> - JCR provide two base implementation of LockManager: + JCR provides two base implementations of the LockManager: </para> - <itemizedlist> + <orderedlist> <listitem> <para> <classname>org.exoplatform.services.jcr.impl.core.lock.LockManagerImpl</classname>; </para> </listitem> <listitem> - <para> - <classname>org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl</classname>; + <para> <classname>org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl</classname>; </para> </listitem> - </itemizedlist> + </orderedlist> <para> - In this article we will talk mostly about CacheableLockManagerImpl. + <classname>LockManagerImpl</classname> is simple implementation of LockManager which is faster than <classname>CacheableLockManager</classname>. It stores lock objects in HashMap and can retain persistant locks if the <literal>LockPersister</literal> is configured. </para> <para> - You can enable LockManager by adding lock-manager-configuration to workspace-configuration. + However, <classname>LockManagerImpl</classname> does not support replication. </para> + <para> + The second implementation (<classname>CacheableLockManagerImpl</classname>) will be the primary focus of this section. + </para> + + <para> + LockManager is enabled by adding <literal>lock-manager-configuration</literal> to <literal>workspace-configuration</literal>. + </para> + <para> For example: </para> -<programlisting><workspace name="ws"> +<programlisting language="XML" role="XML"><![CDATA[<workspace name="ws"> ... - <lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> - <properties> - <property name="time-out" value="15m" /> + <lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> + <properties> + <property name="time-out" value="15m" /> ... - </properties> - </lock-manager> + </properties> + </lock-manager> ... -</workspace> -</programlisting> +</workspace>]]></programlisting> - <section id="sect-Reference_Guide-LockManager_configuration-LockManagerImpl"> - <title>LockManagerImpl</title> - <para> - LockManagerImpl is simple implementation of LockManager, and also faster than CacheableLockManager. It stores Lock objects in HashMap and may also persist Locks if LockPersister is configured. LockManagerImpl do not support replication in any way. - </para> - <para> - See more about LockManager Configuration in <xref linkend="sect-Reference_Guide-eXo_JCR_configuration"/>. - </para> - </section> <section id="sect-Reference_Guide-LockManager_configuration-CacheableLockManagerImpl"> <title>CacheableLockManagerImpl</title> <para> - CacheableLockManagerImpl stores Lock object in JBoss-cache, so Locks are replicable and affects on cluster, not only a single node. Also JBoss-cache has JDBCCacheLoader, so locks will be stored to database. + <classname>CacheableLockManagerImpl</classname> stores lock objects in JBoss-cache (which implements JDBCCacheLoader to store locks in a database). This means its locks are replicable and can affect an entire cluster rather than just a single node. </para> <para> - Both implementation supports Expired Locks removing. There is LockRemover - separate thread, that periodically ask LockManager for Locks that lives to much and must be removed. So, timeout for LockRemover may be set as follows, default value is 30m. + Both implementations support the removal of expired locks. The LockRemover thread periodically polls LockManager for locks that have passed the time-out limit and must be removed. </para> - -<programlisting><properties> - <property name="time-out" value="10m" /> + <para> + The time-out for LockRemover is set as follows (the default value is 30m): + </para> + +<programlisting language="XML" role="XML"><![CDATA[<properties> + <property name="time-out" value="10m" /> ... -</properties> -</programlisting> +</properties>]]></programlisting> + + + <para> - There is few ways how to configure CacheableLockManagerImpl, and all of them configures JBoss-cache and JDBCCacheLoader. + There are a number of ways to configure <classname>CacheableLockManagerImpl</classname>. Each involves configuring JBoss Cache and JDBCCacheLoader. </para> + + <itemizedlist> + <listitem> + <para> + <xref linkend="sect-Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="sect-Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration"/> + </para> + </listitem> + </itemizedlist> <para> - See <ulink url="http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader">http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader</ulink> + Refer to <ulink url="http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader">http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader</ulink> for more information about JBoss Cache and JDBCCacheLoader. </para> - - <formalpara> - <title>Simple JbossCache Configuraion</title> + + + <section id="sect-Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration"> + <title>Simple Jboss Cache Configuration</title> <para> - First one is - put JbossCache configuraion file path to CacheableLockManagerImpl + One method to configure the LockManager is to put a JBoss Cache configuration file path into <classname>CacheableLockManagerImpl</classname>. </para> - </formalpara> + + <note> + <para> + This is not the most efficient method for configuring the LockManager as it requires a JBoss Cache configuration file for each LockManager configuration in each workspace of each repository. The configuration set up can subsequently become quite difficult to manage. + </para> + <para> + This method is useful, however, if a single, specially configured LockManager is required. + </para> + </note> + <para> - <note> - <para> - This configuration is not so good, as you can think. Because repository may contain many workspaces, and each workspace must contain LockManager configuration, and LockManager config may contain JbossCache config file. So total configuration is growing up. But it is usefull if we want a single LockManager with special configuration. - </para> - </note> + The required configuration is shown in the example below: </para> + <programlistingco> + <areaspec> + <area coords="4" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-test-jbosscache-lock-config.xml"/> + </areaspec> + +<programlisting language="XML" role="XML"><![CDATA[<lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> + <properties> + <property name="time-out" value="15m" /> + <property name="jbosscache-configuration" value="conf/standalone/cluster/test-jbosscache-lock-config.xml" /> + </properties> +</lock-manager>]]></programlisting> + + <calloutlist> + <callout arearefs="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-test-jbosscache-lock-config.xml"> + <para> + The <replaceable>test-jbosscache-lock-config.xml</replaceable> is shown below. + </para> + </callout> + </calloutlist> + </programlistingco> + <para> - Config is: + The <filename>test-jbosscache-lock-config.xml</filename> file: </para> + <programlistingco> + <areaspec> + <area coords="5" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-clusterName"/> + <area coords="42" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-cache.jdbc.table.name"/> + <areaset coords="" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-cache.jdbc.types"> + <area coords="49" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-cache.jdbc.node.type"/> + <area coords="46" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-cache.jdbc.fqn.type"/> + </areaset> + </areaspec> -<programlisting><lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> - <properties> - <property name="time-out" value="15m" /> - <property name="jbosscache-configuration" value="conf/standalone/cluster/test-jbosscache-lock-config.xml" /> - </properties> -</lock-manager> -</programlisting> - <para> - <filename>test-jbosscache-lock-config.xml</filename> -<programlisting><?xml version="1.0" encoding="UTF-8"?> -<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.2"> +<programlisting language="XML" role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> +<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.2"> - <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000" /> + <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000" /> - <clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name"> - <stateRetrieval timeout="20000" fetchInMemoryState="false" nonBlocking="true" /> - <jgroupsConfig> + <clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name"> + <stateRetrieval timeout="20000" fetchInMemoryState="false" nonBlocking="true" /> + <jgroupsConfig> - <TCP bind_addr="127.0.0.1" start_port="9800" loopback="true" recv_buf_size="20000000" send_buf_size="640000" discard_incompatible_packets="true" + <TCP bind_addr="127.0.0.1" start_port="9800" loopback="true" recv_buf_size="20000000" send_buf_size="640000" discard_incompatible_packets="true" max_bundle_size="64000" max_bundle_timeout="30" use_incoming_packet_handler="true" enable_bundling="false" use_send_queues="false" sock_conn_timeout="300" skip_suspected_members="true" use_concurrent_stack="true" thread_pool.enabled="true" thread_pool.min_threads="1" thread_pool.max_threads="25" thread_pool.keep_alive_time="5000" thread_pool.queue_enabled="false" thread_pool.queue_max_size="100" thread_pool.rejection_policy="run" oob_thread_pool.enabled="true" oob_thread_pool.min_threads="1" oob_thread_pool.max_threads="8" oob_thread_pool.keep_alive_time="5000" - oob_thread_pool.queue_enabled="false" oob_thread_pool.queue_max_size="100" oob_thread_pool.rejection_policy="run" /> - <MPING timeout="2000" num_initial_members="2" mcast_port="34540" bind_addr="127.0.0.1" mcast_addr="224.0.0.1" /> + oob_thread_pool.queue_enabled="false" oob_thread_pool.queue_max_size="100" oob_thread_pool.rejection_policy="run" /> + <MPING timeout="2000" num_initial_members="2" mcast_port="34540" bind_addr="127.0.0.1" mcast_addr="224.0.0.1" /> - <MERGE2 max_interval="30000" min_interval="10000" /> - <FD_SOCK /> - <FD max_tries="5" shun="true" timeout="10000" /> - <VERIFY_SUSPECT timeout="1500" /> - <pbcast.NAKACK discard_delivered_msgs="true" gc_lag="0" retransmit_timeout="300,600,1200,2400,4800" use_mcast_xmit="false" /> - <UNICAST timeout="300,600,1200,2400,3600" /> - <pbcast.STABLE desired_avg_gossip="50000" max_bytes="400000" stability_delay="1000" /> - <pbcast.GMS join_timeout="5000" print_local_addr="true" shun="false" view_ack_collection_timeout="5000" view_bundling="true" /> - <FRAG2 frag_size="60000" /> - <pbcast.STREAMING_STATE_TRANSFER /> - <pbcast.FLUSH timeout="0" /> + <MERGE2 max_interval="30000" min_interval="10000" /> + <FD_SOCK /> + <FD max_tries="5" shun="true" timeout="10000" /> + <VERIFY_SUSPECT timeout="1500" /> + <pbcast.NAKACK discard_delivered_msgs="true" gc_lag="0" retransmit_timeout="300,600,1200,2400,4800" use_mcast_xmit="false" /> + <UNICAST timeout="300,600,1200,2400,3600" /> + <pbcast.STABLE desired_avg_gossip="50000" max_bytes="400000" stability_delay="1000" /> + <pbcast.GMS join_timeout="5000" print_local_addr="true" shun="false" view_ack_collection_timeout="5000" view_bundling="true" /> + <FRAG2 frag_size="60000" /> + <pbcast.STREAMING_STATE_TRANSFER /> + <pbcast.FLUSH timeout="0" /> - </jgroupsConfig + </jgroupsConfig - <sync /> - </clustering> + <sync /> + </clustering> - <loaders passivation="false" shared="true"> - <preload> - <node fqn="/" /> - </preload> - <loader class="org.jboss.cache.loader.JDBCCacheLoader" async="false" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> - <properties> + <loaders passivation="false" shared="true"> + <preload> + <node fqn="/" /> + </preload> + <loader class="org.jboss.cache.loader.JDBCCacheLoader" async="false" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> + <properties> cache.jdbc.table.name=jcrlocks_ws cache.jdbc.table.create=true cache.jdbc.table.drop=false @@ -183,167 +224,38 @@ cache.jdbc.fqn.column=fqn cache.jdbc.fqn.type=VARCHAR(512) cache.jdbc.node.column=node - cache.jdbc.node.type=<BLOB> + cache.jdbc.node.type=<BLOB> cache.jdbc.parent.column=parent cache.jdbc.datasource=jdbcjcr - </properties> - </loader> + </properties> + </loader> - </loaders> + </loaders> -</jbosscache> -</programlisting> - </para> - <para> - Configuration requirements: - </para> - <itemizedlist> - <listitem> - <para> - <clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name"> - cluster name must be unique; - </para> - </listitem> - <listitem> - <para> - <parameter>cache.jdbc.table.name</parameter> must be unique per datasource; - </para> - </listitem> - <listitem> - <para> - <parameter>cache.jdbc.node.type</parameter> and <parameter>cache.jdbc.fqn.type</parameter> must be configured according to using database. See <xref linkend="tabl-Reference_Guide-Data_Types_in_Different_Databases-Fqn_type_and_node_type_in_different_databases"/>. - </para> - </listitem> - </itemizedlist> - - <formalpara> - <title>Template JBossCache Configuration</title> - <para> - Second one is - use template JBoss-cache configuration for all LockManagers - </para> - </formalpara> - <para> - <citetitle>Lock template configuration</citetitle> - </para> - <para> - <filename>test-jbosscache-lock.xml</filename> - </para> - -<programlisting><?xml version="1.0" encoding="UTF-8"?> -<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> +</jbosscache>]]></programlisting> - <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" - lockAcquisitionTimeout="20000" /> - - <clustering mode="replication" clusterName="${jbosscache-cluster-name}"> - <stateRetrieval timeout="20000" fetchInMemoryState="false" /> - <jgroupsConfig multiplexerStack="jcr.stack" /> - <sync /> - </clustering> - - <loaders passivation="false" shared="true"> -  - <preload> - <node fqn="/" /> - </preload> -  - <pbcast.STATE_TRANSFER /> -  - </config> - </stack> -</protocol_stacks> -</programlisting> - </para> - + </callout> + <callout arearefs="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Simple_Jboss_Cache_Configuration-cache.jdbc.types"> + <para> + The <parameter>cache.jdbc.node.type</parameter> and <parameter>cache.jdbc.fqn.type</parameter> parameters must be configured according to the database in use. + </para> + <para> + Refer to the table below for information about data types. + </para> + </callout> + </calloutlist> + </programlistingco> <table id="tabl-Reference_Guide-Data_Types_in_Different_Databases-Fqn_type_and_node_type_in_different_databases"> <title>Data Types in Different Databases</title> <tgroup cols="3"> @@ -463,6 +375,164 @@ </tbody> </tgroup> </table> + + </section> + + <section id="sect-Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration"> + <title>Template JBoss Cache Configuration</title> + <para> + Another method to configure LockManager is to use a JBoss Cache configuration template for all LockManagers. + </para> + <para> + Below is an example <filename>test-jbosscache-lock.xml</filename> template file: + </para> + <programlistingco> + <areaspec> + <areaset coords="" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> + <area coords="24" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.table.name"/> + <area coords="34" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.datasource"/> + </areaset> + </areaspec> + +<programlisting language="XML" role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> +<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> + + <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" + lockAcquisitionTimeout="20000" /> + + <clustering mode="replication" clusterName="${jbosscache-cluster-name}"> + <stateRetrieval timeout="20000" fetchInMemoryState="false" /> + <jgroupsConfig multiplexerStack="jcr.stack" /> + <sync /> + </clustering> + + <loaders passivation="false" shared="true"> +  + <preload> + <node fqn="/" /> + </preload> +  + <loader class="org.jboss.cache.loader.JDBCCacheLoader" async=q"false" fetchPersistentState="false" + ignoreModifications="false" purgeOnStartup="false"> + <properties> + cache.jdbc.table.name=${jbosscache-cl-cache.jdbc.table.name} + cache.jdbc.table.create=${jbosscache-cl-cache.jdbc.table.create} + cache.jdbc.table.drop=${jbosscache-cl-cache.jdbc.table.drop} + cache.jdbc.table.primarykey=${jbosscache-cl-cache.jdbc.table.primarykey} + cache.jdbc.fqn.column=${jbosscache-cl-cache.jdbc.fqn.column} + cache.jdbc.fqn.type=${jbosscache-cl-cache.jdbc.fqn.type} + cache.jdbc.node.column=${jbosscache-cl-cache.jdbc.node.column} + cache.jdbc.node.type=${jbosscache-cl-cache.jdbc.node.type} + cache.jdbc.parent.column=${jbosscache-cl-cache.jdbc.parent.column} + cache.jdbc.datasource=${jbosscache-cl-cache.jdbc.datasource} + </properties> + </loader> + </loaders> +</jbosscache>]]></programlisting> + + <calloutlist> + <callout arearefs="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> + <para> + All the configurable parameters in this file are populated with templates which will be replaced with LockManager's configuration parameters. + </para> + </callout> + </calloutlist> + </programlistingco> + + <para> + The parameters that will populate the above file are shown below: + </para> + <programlistingco> + <areaspec> + <areaset coords="" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> + <area coords="12" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.fqn.column"/> + <area coords="15" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.node.type"/> + </areaset> + <area coords="5" id="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml"/> + </areaspec> + +<programlisting language="XML" role="XML"><![CDATA[<lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> + <properties> + <property name="time-out" value="15m" /> + <property name="jbosscache-configuration" value="test-jbosscache-lock.xml" /> + <property name="jgroups-configuration" value="udp-mux.xml" /> + <property name="jgroups-multiplexer-stack" value="true" /> + <property name="jbosscache-cluster-name" value="JCR-cluster-locks-ws" /> + <property name="jbosscache-cl-cache.jdbc.table.name" value="jcrlocks_ws" /> + <property name="jbosscache-cl-cache.jdbc.table.create" value="true" /> + <property name="jbosscache-cl-cache.jdbc.table.drop" value="false" /> + <property name="jbosscache-cl-cache.jdbc.table.primarykey" value="jcrlocks_ws_pk" /> + <property name="jbosscache-cl-cache.jdbc.fqn.column" value="fqn" /> + <property name="jbosscache-cl-cache.jdbc.fqn.type" value="AUTO"/> + <property name="jbosscache-cl-cache.jdbc.node.column" value="node" /> + <property name="jbosscache-cl-cache.jdbc.node.type" value="AUTO"/> + <property name="jbosscache-cl-cache.jdbc.parent.column" value="parent" /> + <property name="jbosscache-cl-cache.jdbc.datasource" value="jdbcjcr" /> + </properties> +</lock-manager>]]></programlisting> + + <calloutlist> + <callout arearefs="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> + <para> + The <parameter>jbosscache-cl-cache.jdbc.fqn.column</parameter> and <parameter>jbosscache-cl-cache.jdbc.node.type</parameter> parameters are not explicitly defined as <parameter>cache.jdbc.fqn.type</parameter> and <parameter>cache.jdbc.node.type</parameter> are defined in the JBoss Cache configuration. + </para> + <para> + Refer to <xref linkend="tabl-Reference_Guide-Data_Types_in_Different_Databases-Fqn_type_and_node_type_in_different_databases"/> for information about setting these parameters or set them as <parameter>AUTO</parameter> and the data type will by detected automatically. + </para> + </callout> + <callout arearefs="Reference_Guide-LockManager_configuration-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml"> + <para> + The <literal>jgroups-configuration</literal> has been moved to a separate configuration file (<filename>udp-mux.xml</filename>, shown below). + </para> + <para> + In this case the <filename>udp-mux.xml</filename> is a common configuration for all JGroup components (QueryHandler, cache, LockManager), but this is not a requirement of the configuration method. + </para> + </callout> + </calloutlist> + </programlistingco> + + <para> + <filename>udp-mux.xml</filename>: + </para> + +<programlisting language="XML" role="XML"><![CDATA[<protocol_stacks> + <stack name="jcr.stack"> + <config> + <UDP mcast_addr="228.10.10.10" mcast_port="45588" tos="8" ucast_recv_buf_size="20000000" + ucast_send_buf_size="640000" mcast_recv_buf_size="25000000" mcast_send_buf_size="640000" loopback="false" + discard_incompatible_packets="true" max_bundle_size="64000" max_bundle_timeout="30" + use_incoming_packet_handler="true" ip_ttl="2" enable_bundling="true" enable_diagnostics="true" + thread_naming_pattern="cl" use_concurrent_stack="true" thread_pool.enabled="true" thread_pool.min_threads="2" + thread_pool.max_threads="8" thread_pool.keep_alive_time="5000" thread_pool.queue_enabled="true" + thread_pool.queue_max_size="1000" thread_pool.rejection_policy="discard" oob_thread_pool.enabled="true" + oob_thread_pool.min_threads="1" oob_thread_pool.max_threads="8" oob_thread_pool.keep_alive_time="5000" + oob_thread_pool.queue_enabled="false" oob_thread_pool.queue_max_size="100" oob_thread_pool.rejection_policy="Run" /> + + <PING timeout="2000" num_initial_members="3" /> + <MERGE2 max_interval="30000" min_interval="10000" /> + <FD_SOCK /> + <FD timeout="10000" max_tries="5" shun="true" /> + <VERIFY_SUSPECT timeout="1500" /> + <BARRIER /> + <pbcast.NAKACK use_stats_for_retransmission="false" exponential_backoff="150" use_mcast_xmit="true" + gc_lag="0" retransmit_timeout="50,300,600,1200" discard_delivered_msgs="true" /> + <UNICAST timeout="300,600,1200" /> + <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000" max_bytes="1000000" /> + <VIEW_SYNC avg_send_interval="60000" /> + <pbcast.GMS print_local_addr="true" join_timeout="3000" shun="false" view_bundling="true" /> + <FC max_credits="500000" min_threshold="0.20" /> + <FRAG2 frag_size="60000" /> +  + <pbcast.STATE_TRANSFER /> +  + </config> + </stack> +</protocol_stacks>]]></programlisting> + + </section> </section> </section> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-05-19 07:37:40 UTC (rev 3121) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-05-19 07:47:16 UTC (rev 3122) @@ -6,165 +6,139 @@ <section id="sect-Reference_Guide-QueryHandler_configuration"> <title>QueryHandler configuration</title> <para> - Lets talk about indexing content in cluster. + Indexing content in a cluster can be problematic as indexes cannot be replicated across nodes. Data present and indexed on one node will not be indexed if it is replicated to another. </para> + <para> - For couple of reasons, we can't replicate index. That's means, some data added and indexed on one cluster node, will be replicated to another cluster node, but will not be indexed on that node. + This problem can be overcome with the use of a <emphasis>coordinator-node</emphasis>. A coordinator-node can maintain a Lucene index of the data on a cluster. </para> <para> - <citetitle>So, how do the indexing works in cluster environment?</citetitle> + The coordinator-node is chosen automatically, so there is no need for any special configuration. </para> <para> - As, we can not index same data on all nodes of cluster, we must index it on one node. Node, that can index data and do changes on lucene index, is called "coordinator". Coordinator-node is choosen automaticaly, so we do not need special configuration for coordinator. + Other nodes in the cluster deliver indexing request messages to JBoss Cache. The coordinator retrieves those messages and updates the index accordingly. </para> <para> - But, how can another nodes save their changes to lucene index? + Searching data on a cluster can be likewise problematic, as search engines are unable to work with the index/coordinator model proposed above. Therefore each node in the cluster must be configured to access the Lucene index from a shared directory. However the coordinator reserves the ability to edit that index. </para> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/Advanced/JCR/diagram-shared-index.png" format="PNG" align="center" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/Advanced/JCR/diagram-shared-index.png" format="PNG" align="center" contentwidth="140mm" /> + </imageobject> + </mediaobject> + <para> - First of all, data is already saved and replicated to another cluster-nodes, so we need only deliver message like "we need to index this data" to coordinator. Thats why Jboss-cache is used. + Regardless of whether they are running in a clustered environment or not, Indexers do not writes changes to the file system Lucene index immediately. The data is written to a volatile index first. </para> <para> - All nodes of cluster writes messages into JBoss-cache but only coordinator takes those messages and makes changes Lucene index. + If (or when) the volatile index size reaches or exceeds 1 Mb it is flushed to the shared file system index. Volatile indexes can also be flushed after a given time. The volatile index time out is configured with the "<parameter>max-volatile-time</parameter>" parameter. </para> <para> - <citetitle>How do the search works in cluster environment?</citetitle> + Refer to <xref linkend="sect-Reference_Guide-Search_Configuration"/> for more information. </para> - <para> - Search engine do not works with indexer, coordinator, etc. Search needs only lucene index. But only one cluster node can change lucene index - asking you. Yes - lucene index is shared. So, all cluster nodes must be configured to use lucene index from shared directory. - </para> - <para> - A little bit about indexing process (no matter, cluster or not) Indexer do not writes changes to FS lucene index immediately. At first, Indexer writes changes to Volatile index. If Volatile index size become 1Mb or more it is flushed to FS. Also there is timer, that flushes volatile index by timeout. Volatile index timeout configured by "max-volatile-time" paremeter. - </para> - <para> - See more in <xref linkend="sect-Reference_Guide-Search_Configuration"/>. - </para> - <para> - Common scheme of Shared Index - <mediaobject> - <imageobject> - <imagedata fileref="images/Advanced/JCR/diagram-shared-index.png" format="PNG" width="444" /> - </imageobject> - </mediaobject> - </para> + <section id="sect-Reference_Guide-QueryHandler_configuration-Configuration"> <title>Configuration</title> <formalpara> <title>Common requirements</title> <para> - Now, lets see what we need to run Search engine in cluster environment. + The following requirements must be met to run a search engine in clustered environment: </para> </formalpara> - <itemizedlist> + <orderedlist> <listitem> <para> - shared directory for storing Lucene index (i.e. NFS); + A shared directory for storing the Lucene index (an NFS mounted directory, for example); </para> </listitem> <listitem> <para> - changes filter configured as org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter; + A JBoss Cache changes filter configured as <parameter>org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter</parameter>: </para> <note> <para> - This filter ignore changes on non-coordinator nodes, and index changes on coordinator node. + This filter ignores changes on non-coordinator nodes and indexes changes on the coordinator node. </para> </note> </listitem> <listitem> <para> - configure JBoss-cache, course; + A correctly configured instance of JBoss Cache; </para> </listitem> - </itemizedlist> + </orderedlist> <formalpara> <title>Query-handler configuration</title> <para> - Configuration example: + An example configuration </para> </formalpara> -<programlisting><workspace name="ws"> - <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> - <properties> - <property name="index-dir" value="shareddir/index/db1/ws" /> - <property name="changesfilter-class" - value="org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter" /> - <property name="jbosscache-configuration" value="jbosscache-indexer.xml" /> - <property name="jgroups-configuration" value="udp-mux.xml" /> - <property name="jgroups-multiplexer-stack" value="true" /> - <property name="jbosscache-cluster-name" value="JCR-cluster-indexer-ws" /> - <property name="max-volatile-time" value="60" /> - </properties> - </query-handler> -</workspace> -</programlisting> - <table id="tabl-Reference_Guide-Query_handler_configuration-Config_properties_description"> - <title>Config properties description</title> - <tgroup cols="2"> - <thead> - <row> - <entry> - Property name - </entry> - <entry> - Description - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - index-dir - </entry> - <entry> - path to index - </entry> - </row> - <row> - <entry> - jbosscache-configuration - </entry> - <entry> - template of JBoss-cache configuration for all query-handlers in repository - </entry> - </row> - <row> - <entry> - jgroups-configuration - </entry> - <entry> - jgroups-configuration is template configuration for all components (search, cache, locks)  - </entry> - </row> - <row> - <entry> - jgroups-multiplexer-stack - </entry> - <entry> - If "jgroups-multiplexer-stack" is true and "jgroups-configuration" parameters are set then Multiplexing stack is enabled in JBossCache. - </entry> - </row> - <row> - <entry> - jbosscache-cluster-name - </entry> - <entry> - cluster name (must be unique) - </entry> - </row> - <row> - <entry> - max-volatile-time - </entry> - <entry> - max time to live for Volatile Index - </entry> - </row> - </tbody> - </tgroup> - </table> + + <programlistingco> + <areaspec> + <area coords="4" id="Reference_Guide-QueryHandler_configuration-Configuration-index-dir"/> + <area coords="8" id="Reference_Guide-QueryHandler_configuration-Configuration-jbosscache-configuration"/> + <area coords="9" id="Reference_Guide-QueryHandler_configuration-Configuration-jgroups-configuration"/> + <area coords="10" id="Reference_Guide-QueryHandler_configuration-Configuration-jgroups-multiplexer-stack"/> + <area coords="11" id="Reference_Guide-QueryHandler_configuration-Configuration-jbosscache-cluster-name"/> + <area coords="12" id="Reference_Guide-QueryHandler_configuration-Configuration-max-volatile-time"/> + </areaspec> +<programlisting language="" role=""><![CDATA[<workspace name="ws"> + <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> + <properties> + <property name="index-dir" value="shareddir/index/db1/ws" /> + <property name="changesfilter-class" + value="org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter" /> + <property name="jbosscache-configuration" value="jbosscache-indexer.xml" /> + <property name="jgroups-configuration" value="udp-mux.xml" /> + <property name="jgroups-multiplexer-stack" value="true" /> + <property name="jbosscache-cluster-name" value="JCR-cluster-indexer-ws" /> + <property name="max-volatile-time" value="60" /> + </properties> + </query-handler> +</workspace>]]></programlisting> + + <calloutlist> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-index-dir"> + <para> + The <parameter>index-dir</parameter> property is the path to the index directory. + </para> + </callout> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-jbosscache-configuration"> + <para> + The <parameter>jbosscache-configuration</parameter> property is the configuration template for all query-handlers in the repository + </para> + </callout> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-jgroups-configuration"> + <para> + The <parameter>jgroups-configuration</parameter> property is the configuration template for all components (search, cache, locks).  + </para> + </callout> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-jgroups-multiplexer-stack"> + <para> + When the <parameter>jgroups-multiplexer-stack</parameter> property is set to <emphasis>true</emphasis> (and appropriate <parameter>jgroups-configuration</parameter> paramters are set) then Multiplexing stack is enabled in JBoss Cache. + </para> + </callout> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-jbosscache-cluster-name"> + <para> + The <parameter>jbosscache-cluster-name</parameter> property is the cluster name. This name must be unique. + </para> + </callout> + <callout arearefs="Reference_Guide-QueryHandler_configuration-Configuration-max-volatile-time"> + <para> + The <parameter>max-volatile-time</parameter> property controls the time-out period between volatile index flushes. + </para> + </callout> + + </calloutlist> + </programlistingco> + <formalpara> <title>JBoss-Cache template configuration</title> <para>

14 years, 1 month

1
0
0 / 0

gatein SVN: r3121 - portal/trunk/web/portal/src/main/webapp/groovy/portal/webui/container.

by do-not-reply＠jboss.org

Author: trong.tran Date: 2010-05-19 03:37:40 -0400 (Wed, 19 May 2010) New Revision: 3121 Modified: portal/trunk/web/portal/src/main/webapp/groovy/portal/webui/container/UIContainer.gtmpl Log: GTNPORTAL-1045 Add a new CSS class for handling a empty container while editting layout Modified: portal/trunk/web/portal/src/main/webapp/groovy/portal/webui/container/UIContainer.gtmpl =================================================================== --- portal/trunk/web/portal/src/main/webapp/groovy/portal/webui/container/UIContainer.gtmpl 2010-05-19 07:18:12 UTC (rev 3120) +++ portal/trunk/web/portal/src/main/webapp/groovy/portal/webui/container/UIContainer.gtmpl 2010-05-19 07:37:40 UTC (rev 3121) @@ -42,7 +42,7 @@ <div class="VIEW-CONTAINER VIEW-BLOCK"> <%} %> <%if(hasPermission) {%> - <div class="UIRowContainer"> + <div class="UIRowContainer <%=uicomponent.getChildren().size() == 0 ? "EmptyContainer" : ""%>"> <div> <%uicomponent.renderChildren();%> </div>

14 years, 1 month

1
0
0 / 0

gatein SVN: r3120 - maven/packager/trunk.

by do-not-reply＠jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-05-19 03:18:12 -0400 (Wed, 19 May 2010) New Revision: 3120 Modified: maven/packager/trunk/pom.xml Log: Use new parent and new Nexus repo Modified: maven/packager/trunk/pom.xml =================================================================== --- maven/packager/trunk/pom.xml 2010-05-19 07:02:56 UTC (rev 3119) +++ maven/packager/trunk/pom.xml 2010-05-19 07:18:12 UTC (rev 3120) @@ -22,7 +22,7 @@ <parent> <groupId>org.gatein</groupId> <artifactId>gatein-parent</artifactId> - <version>1.0.0-GA</version> + <version>1.0.1-GA</version> </parent> <modelVersion>4.0.0</modelVersion> @@ -42,27 +42,20 @@  <repositories> - <repository> - <id>repository.jboss.org</id> - <name>JBoss Repository</name> - <layout>default</layout> - <url>http://repository.jboss.org/maven2/</url> - <snapshots> - <enabled>false</enabled> - </snapshots> - </repository> - <repository> - <id>snapshots.jboss.org</id> - <name>JBoss Snapshots Repository</name> - <layout>default</layout> - <url>http://snapshots.jboss.org/maven2/</url> - <snapshots> - <enabled>true</enabled> - </snapshots> - <releases> - <enabled>false</enabled> - </releases> - </repository> + <repository> + <id>jboss-public-repository-group</id> + <name>JBoss Public Maven Repository Group</name> + <url>https://repository.jboss.org/nexus/content/groups/public/</url> + <layout>default</layout> + <releases> + <enabled>true</enabled> + <updatePolicy>never</updatePolicy> + </releases> + <snapshots> + <enabled>true</enabled> + <updatePolicy>never</updatePolicy> + </snapshots> + </repository> </repositories> <build>

14 years, 1 month

1
0
0 / 0

gatein SVN: r3119 - maven/packager/trunk/src/main/javascript/eXo/server.

by do-not-reply＠jboss.org

Author: thomas.heute(a)jboss.com Date: 2010-05-19 03:02:56 -0400 (Wed, 19 May 2010) New Revision: 3119 Modified: maven/packager/trunk/src/main/javascript/eXo/server/Tomcat.js Log: GTNPORTAL-1181: Tomcat packaging Modified: maven/packager/trunk/src/main/javascript/eXo/server/Tomcat.js =================================================================== --- maven/packager/trunk/src/main/javascript/eXo/server/Tomcat.js 2010-05-19 06:46:54 UTC (rev 3118) +++ maven/packager/trunk/src/main/javascript/eXo/server/Tomcat.js 2010-05-19 07:02:56 UTC (rev 3119) @@ -128,7 +128,19 @@ // Copy sample skin in the deploy directory without affecting gatein.ear/META-INF/application.xml eXo.core.IOUtil.cp(eXo.env.currentDir + "/../../examples/skins/simpleskin/target/gatein-sample-skin.war", this.deployWebappDir); - + // Delete confusing files + eXo.core.IOUtil.remove(this.serverHome + "/bin/startup.sh"); + eXo.core.IOUtil.remove(this.serverHome + "/bin/startup.bat"); + eXo.core.IOUtil.remove(this.serverHome + "/bin/shutdown.sh"); + eXo.core.IOUtil.remove(this.serverHome + "/bin/shutdown.bat"); + eXo.core.IOUtil.remove(this.serverHome + "/RUNNING.txt"); + eXo.core.IOUtil.cp(this.serverHome + "/LICENSE", this.serverHome + "/TOMCAT-LICENSE"); + eXo.core.IOUtil.remove(this.serverHome + "/LICENSE"); + eXo.core.IOUtil.cp(this.serverHome + "/RELEASE-NOTES", this.serverHome + "/TOMCAT-RELEASE-NOTES"); + eXo.core.IOUtil.remove(this.serverHome + "/RELEASE-NOTES"); + eXo.core.IOUtil.cp(this.serverHome + "/NOTICE", this.serverHome + "/TOMCAT-NOTICE"); + eXo.core.IOUtil.remove(this.serverHome + "/NOTICE"); + var configFileInWar = "WEB-INF/conf/configuration.xml"; var portalwar = new java.io.File(this.deployWebappDir + "/" + product.portalwar); eXo.System.info("CONF", "Patching " + configFileInWar + " in " + portalwar + " : remove wsrp configuration");

14 years, 1 month

1
0
0 / 0

gatein SVN: r3118 - portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2010-05-19 02:46:54 -0400 (Wed, 19 May 2010) New Revision: 3118 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Book_Info.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Release_Notes.xml Log: JBEPP-279: Added content to Features, Migration and Tech Preview sections as per email from jandersen Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Book_Info.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Book_Info.xml 2010-05-19 04:59:05 UTC (rev 3117) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Book_Info.xml 2010-05-19 06:46:54 UTC (rev 3118) @@ -3,14 +3,14 @@ ]> <articleinfo id="arti-Release_Notes-Release_Notes"> <title>Release Notes</title> - <subtitle>For use with JBoss Enterprise Portal Platform 5.0</subtitle> + <subtitle>For use with JBoss Enterprise Portal Platform 5.0.0</subtitle> <edition>1.0</edition> <pubsnumber>1</pubsnumber> <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.0</productnumber> + <productnumber>5.0.0</productnumber> <abstract> <para> - These release notes contain important information related to JBoss Enterprise Portal Platform 5.0 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Portal Platform 5.0. + These release notes contain important information related to JBoss Enterprise Portal Platform 5.0 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Portal Platform 5.0.0. </para> </abstract> <isbn>N/A</isbn> Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Release_Notes.xml =================================================================== --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Release_Notes.xml 2010-05-19 04:59:05 UTC (rev 3117) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes/en-US/Release_Notes.xml 2010-05-19 06:46:54 UTC (rev 3118) @@ -15,12 +15,123 @@ <section> <title>New Features</title> - <warning> - <title>TODO</title> - <para> - Input from Jason here - </para> - </warning> + <variablelist> + <varlistentry> + <term>Revamped User Interface</term> + <listitem> + <para> + JBoss Enterprise Portal Platform (<emphasis role="bold">EPP</emphasis>) has replaced it's existing JSF user interface with one based upon a new framework that is an extension of the Groovy framework. This new interface includes many new features geared towards enabling more interaction and customization of portals, skins and pages by non-development resources. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Master Object Page Model </term> + <listitem> + <para> + EPP has replaced the existing XML file drive page model towards a new model that treats each portlet page as an object stored in the Java Content Repository. This new model allows for pages to be highly reusable and enables simple page creation, editing and hierarchical node management within the portal. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>New Navigational Controls</term> + <listitem> + <para> + EPP has implemented navigational controls that dynamically and contextually get data from the JCR. These controls are portlet based and can be customized and modified to meet a wide range of navigational options. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Site and Page Wizards</term> + <listitem> + <para> + EPP has implemented wizard capabilities to simplify the creation of pages for non-development resources. These wizards enable selection of page placement in the portal, implenmentation of over 10 out of the box page layouts, addition of portlets and gadgets as well as page security. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Adminsitration Portlets</term> + <listitem> + <para> + EPP has implemented an entirely new set of administration portlets to simplify the management of portlets and gadgets and well as users and groups. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Right to Left Language Support</term> + <listitem> + <para> + EPP supports localization and includes over 12 out of the box language localizations. This includes right to left language support. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Gadget Container</term> + <listitem> + <para> + EPP has implemented the Shindig Open Social Gadget container. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Portlet Bridge 2.0</term> + <listitem> + <para> + A new updated version of the Portlet Bridge Project that enables the easy creation of portlets that reuse JSF, Seam and Rich Faces applications. The new version of the bridge spans a wider range of use cases from the underlying applications as well as support for the Portlet 2.0 (JSR286) specification. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Example Portlets</term> + <listitem> + <para> + EPP includes a directory with additional example and sample portlets that can be compiled and modified to meet customer requirements in projects. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>New Identity Manager</term> + <listitem> + <para> + A new framework to manage users, groups and roles is implemented. This new idenitity manager enables attributes to utilize information from LDAP servers as well as external databases and applications + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>JBoss Enterprise Application Server 5.0</term> + <listitem> + <para> + The JBoss Enterprise Application Server 5.0 (JBoss EAP 5.0) is based on the JBoss AS 5.1.x family and is the latest release of the world's most popular application server. JBoss EAP 5.0 represents the state of the art with the second generation JBoss Microcontainer-based enterprise Java run-time. + </para> + <para> + In addition to supporting the latest Java EE specification (Java EE 5), JBoss EAP 5.0 integrates many of the best enterprise class services for advanced messaging, persistence, transactions, caching and high-availability. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>JBoss Microcontainer</term> + <listitem> + <para> + The JBoss Microcontainer is a refactoring of the modular JBoss JMX Microkernel. It is a lightweight kernel that manages the loading, lifecycle and dependencies between POJOs. Together with a Servlet/JSP container, an EJB container, deployers, and management utilities, the JBoss Microcontainer provides a standard Java EE 5 profile. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>JBoss Cache</term> + <listitem> + <para> + JBoss Cache provides replication for EJB and HTTP session state and supports distributed entity caching for JPA. It also provides superior performance and scalability with the new MultiVersion Concurrency Control (MVCC) locking scheme. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>JBoss Web Services</term> + <listitem> + <para> + JBoss Web Services is a framework that provides support for the latest JAX-WS specification as well as a plugin architecture for supporting alternative Web Services Stacks. + </para> + </listitem> + </varlistentry> + </variablelist> </section> <section id="sect-Release_Notes-Architecture_of_PRODUCT_VERSION"> @@ -515,12 +626,14 @@ <section id="sect-Release_Notes-_Known_Issues_with_this_release_"> <title> Known Issues with this release </title> - <warning> - <title>TODO</title> + <para> - The list below provides a list of issues being tracked at the time of release: + JBoss Enterprise Portal Platform 5.0 is based upon an entirely new JBoss community project named GateIn <ulink type="http" url="http://www.gatein.org">www.gatein.org</ulink>). Previous releases were based upon the JBoss Portal Community Project <ulink type="http" url="http://www.jbossportal.org">www.jbossportal.org</ulink>). </para> - </warning> + <para> + Every reasonable effort has been made to address issues with the previous releases of Enterprise Portal Platform. However, since this is a completely new architecture it is difficult to provide a pure translation of issues from release to release. + </para> + <formalpara id="form-Release_Notes-_Known_Issues_with_this_release_-General_Known_Issues"> <title>General Known Issues</title> <para> @@ -570,29 +683,16 @@ <section> <title>Migration from JBoss Portal 4.3</title> <para> - Read this section to learn about the differences between JBoss Enterprise Portal Platform 5.0 and previous versions that may cause difficulties when moving your applications to version 5.0. + As stated in section 5 of this document, Enterprise Portal Platform 5 is based upon an entirely new core architecture and is not backwards compatible with Enterprise Portal Platform 4.3. </para> - <para> - As a matter of best practice, Red Hat recommends that you test this new version of the JBoss Enterprise Portal Platform thoroughly before deploying it in your production environment. + <para> + As a value added part of an enterprise subscription to EPP the JBoss Portal team is working to develop a set of migration utilities (which may take the form of documentation, guides and/or scripts) to assist customers in migration. We intend to release these utilities in a future revision of JBoss Enterprise Portal Platform 5.x. </para> - <warning> - <title>TODO</title> - <para> - This is a real issue for EPP 5.0. - -- Need PM type overview of types of challenges, context, - and such with diplomatic wording. - -- Also need either technical details, or pointer to where - KBase or other help will be, or recommendation to - pay for professional services, or... - -- Ref: SOA500 RN has a chapter 9 like this. - ==> Jason can you offer guidance on this section? - </para> - </warning> <para> - Customers are advised to contact Red Hat JBoss Support for migration advice before deploying &PRODUCT; into a production environment. + For customers seeking to begin a migration prior to the availability of any Red Hat provided migration utilities, please contact Red Hat JBoss Support for migration advice. Red Hat JBoss support will be the main communication channel for migration knowledge as it is developed. </para> <para> - The JBoss Customer Support Portal can be accessed <ulink type="http" url="https://www.redhat.com/apps/support/">here</ulink>. + Red Hat JBoss Customer Support can be accessed <ulink type="http" url="https://www.redhat.com/apps/support/">here</ulink>. </para> </section> @@ -612,10 +712,7 @@ <section> <title>Site Publisher</title> <para> - Required if Site Publisher Tech Preview included - Ref: EAP500 [1] has chapter 9 for CXFF and mod_cluster - ==> TODO: Jason guidance - + EPP also includes an optional download from the Red Hat Customer Support Portal for a technical preview for an optional add on called Site Publisher. Site Publisher is an embedded web content authoring and publication component that provides many addtional features for organizations looking to enable line of business resources to directly manage sites, pages and content within the context of the portal versus through integration with an external web content management system. </para> </section> </section> --> @@ -634,7 +731,7 @@ <term>Installation Guide</term> <listitem> <para> - This document explains how to install and verify the installation of &PRODUCT; using different installation modes. + This document explains how to install and verify the installation of &PRODUCT; using different installation methods. </para> <para> Get the Installation Guide from <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.0.0/h...">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.0.0/h...</ulink> @@ -656,7 +753,7 @@ <term>Reference Guide</term> <listitem> <para> - This is a high-level usage document. It deals with more advanced topics than the Install and User guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of &PRODUCT;. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. + This is a high-level usage document. It deals with more advanced topics than the Installation and User guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of &PRODUCT;. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. </para> <para> Get the Reference Guide from <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.0.0/h...">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.0.0/h...</ulink>

14 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits May 2010