From do-not-reply at jboss.org Mon May 24 01:29:10 2010 Content-Type: multipart/mixed; boundary="===============7384857987569668955==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: gatein-commits at lists.jboss.org Subject: [gatein-commits] gatein SVN: r3182 - in portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules: Advanced/JCR and 5 other directories. Date: Mon, 24 May 2010 01:29:10 -0400 Message-ID: <201005240529.o4O5TA0j030891@svn01.web.mwc.hst.phx2.redhat.com> --===============7384857987569668955== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2010-05-24 01:29:09 -0400 (Mon, 24 May 2010) New Revision: 3182 Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/Advanced/JCR/search-configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/Advanced/JCR/statistics.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationTokenConfigu= ration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurati= on.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.= xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/PortletDevelopment/Standard.xml portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen= ce_Guide/en-US/modules/WSRP.xml Log: JBEPP-276: Further QE edits. Outstanding issues in JIRA comment 24/May/10 0= 1:28 AM Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml 2010-0= 5-24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml 2010-0= 5-24 05:29:09 UTC (rev 3182) @@ -8,7 +8,7 @@
Introduction - JBossTransactionsService implements eXo and provides access to JBoss Transaction Service (JBossTS) JTA imp= lementation via eXo container dependency. + JBossTransactionsService implements eXo JCR and provides access to JBoss Transaction Se= rvice (JBossTS) JTA implementation via eXo container dependency. TransactionService used in JCR cache org.exoplatform.services= .jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache implementation. = Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-05= -24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-05= -24 05:29:09 UTC (rev 3182) @@ -395,7 +395,7 @@ - For information on defining other parameters, refer to the Apache DBCP = configuration + For information on defining other parameters, refer to the Apache DBC= P configuration at http://jakarta.apache.org/commons/dbcp/configuration.html<= /ulink> @@ -596,41 +596,39 @@ The following example shows the settings for embedded mode for the jdbcjcr data container: = -<external-component-plugins> - <target-component>org.exoplatform.services.naming.InitialContext= Initializer</target-component> - <component-plugin> - <name>bind.datasource</name> - <set-method>addPlugin</set-method> - <type>org.exoplatform.services.naming.BindReferencePlugin<= ;/type> - <init-params> - <value-param> - <name>bind-name</name> - <value>jdbcjcr</value> - </value-param> - <value-param> - <name>class-name</name> - <value>javax.sql.DataSource</value> - </value-param> - <value-param> - <name>factory</name> - <value>org.apache.commons.dbcp.BasicDataSourceFactory<= ;/value> - </value-param> - <properties-param> - <name>ref-addresses</name> - <description>ref-addresses</description> - <property name=3D"driverClassName" value=3D"org.postgresql.= Driver"/> - <property name=3D"url" value=3D"jdbc:postgresql://exoua.dns= alias.net/portal"/> - <property name=3D"username" value=3D"exoadmin"/> - <property name=3D"password" value=3D"exo12321"/> - <property name=3D"maxActive" value=3D"50"/> - <property name=3D"maxIdle" value=3D"5"/> - <property name=3D"initialSize" value=3D"5"/> - </properties-param> - </init-params> - </component-plugin> - </external-component-plugins> - - + + org.exoplatform.services.naming.InitialContextInitia= lizer + + bind.datasource + addPlugin + org.exoplatform.services.naming.BindReferencePlugin + + + bind-name + jdbcjcr + + + class-name + javax.sql.DataSource + + + factory + org.apache.commons.dbcp.BasicDataSourceFactory + + + ref-addresses + ref-addresses + + + + + + + + + + + ]]> To configure multiple repository workspaces with a single database the = "multi-db" parameter must be switched off (set the value to "false"). @@ -638,64 +636,63 @@ The following example shows configuration for two workspaces ws (jdbcjcr) and ws1 (jdbcjcr) which wi= ll be persisted in one PostgreSQL database: = -<workspaces> - <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured"> - <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.= JDBCWorkspaceDataContainer"> - <properties> - <property name=3D"source-name" value=3D"jdbcjcr"/> - <property name=3D"dialect" value=3D"pgsql"/> - <property name=3D"multi-db" value=3D"false"/> - <property name=3D"max-buffer-size" value=3D"200K"/> - <property name=3D"swap-directory" value=3D"target/temp/swap/ws"/&= gt; - </properties> - </container> - <cache enabled=3D"true"> - <properties> - <property name=3D"max-size" value=3D"10K"/> - <property name=3D"live-time" value=3D"30m"/> - </properties> - </cache> - <query-handler class=3D"org.exoplatform.services.jcr.impl.core.quer= y.lucene.SearchIndex"> - <properties> - <property name=3D"index-dir" value=3D"../temp/index"/> - </properties> - </query-handler> - <lock-manager> - <time-out>15m</time-out> - <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil= eSystemLockPersister"> - <properties> - <property name=3D"path" value=3D"target/temp/lock/ws"/> - </properties> - </persister> - </lock-manager> - </workspace> - <workspace name=3D"ws1" auto-init-root-nodetype=3D"nt:unstructured"&g= t; - <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.= JDBCWorkspaceDataContainer"> - <properties> - <property name=3D"source-name" value=3D"jdbcjcr"/> - <property name=3D"dialect" value=3D"pgsql"/> - <property name=3D"multi-db" value=3D"false"/> - <property name=3D"max-buffer-size" value=3D"200K"/> - <property name=3D"swap-directory" value=3D"target/temp/swap/ws1"/= > - </properties> - </container> - <cache enabled=3D"true"> - <properties> - <property name=3D"max-size" value=3D"10K"/> - <property name=3D"live-time" value=3D"5m"/> - </properties> - </cache> - <lock-manager> - <time-out>15m</time-out> - <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil= eSystemLockPersister"> - <properties> - <property name=3D"path" value=3D"target/temp/lock/ws1"/> - </properties> - </persister> - </lock-manager> - </workspace> -</workspaces> - + + + + + + + + + + + + + + + + + + + + + + + + 15m + + + + + + + + + + + + + + + + + + + + + + + + + 15m + + + + + + + +]]> =
Configuration without DataSource @@ -715,16 +712,15 @@ = -<workspace name=3D"ws" auto-init-root-nodetype=3D"nt:un= structured"> - <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.JD= BCWorkspaceDataContainer"> - <properties> - <property name=3D"dialect" value=3D"hsqldb"/> - <property name=3D"driverClassName" value=3D"org.hsqldb.jdbcDriver= "/> - <property name=3D"url" value=3D"jdbc:hsqldb:file:target/temp/data= /portal"/> - <property name=3D"username" value=3D"su"/> - <property name=3D"password" value=3D""/> = - ...... - + + + + + + + + = + ......]]> Ensure the JDBC driver provides connection pooling. Connection poolin= g is required for use with JCR to prevent a database overload. @@ -784,13 +780,13 @@ org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDa= taContainer: = -<workspaces> - <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured"> - <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.= JDBCWorkspaceDataContainer"> + + + ... - </workspace> -</worksapces> - + +]]> + Simple queries are implemented in such a way so as to support as many d= atabase dialects as possible. They do not use sub queries, or left or right= joins. @@ -798,13 +794,14 @@ Complex queries will be used if you choose org.exoplatform.s= ervices.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer: -<workspaces> - <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured"> - <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.= optimisation.CQJDBCWorkspaceDataContainer"> + + + + ... - </workspace> -</worksapces> - + +]]> + Complex queries are optimized to reduce the number of requests made to = a database. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/Advanced/JCR/search-configuration.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2010-05-24 02= :58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/Advanced/JCR/search-configuration.xml 2010-05-24 05= :29:09 UTC (rev 3182) @@ -41,28 +41,29 @@ ]]> = - - - Due to sizing constraints in the table below, all references to classes= or values that begin with the string org.exoplatform.services.jcr= .impl.core.query.lucene will be refered to as $lucene.identifier. - - - For example; org.exoplatform.services.jcr.impl.core.query.luce= ne.SearchIndex will appear as $lucene.SearchIndex - - - +
Configuration parameters + + + - Parameter + + Parameter + - Default + + Default + - Description + + Description + - min-merge-docs + + min-merge-docs + - 100 + + 100 + - The minimum number of nodes in an index until segments are merged. + + The minimum number of nodes in an index until segments are merged. + - volatile-idle-time + + volatile-idle-time + 3 - Idle time in seconds until the volatile index part is moved to a pe= rsistent index even though minMergeDocs is not reached. + + Idle time in seconds until the volatile index part is moved to a p= ersistent index even though minMergeDocs is not reached. + - max-merge-docs + + max-merge-docs + - Integer.MAX_VALUE + + Integer.MAX_VALUE + - The maximum number of nodes in segments that will be merged. The de= fault value changed to Integer.MAX_VALUE in JCR version = 1.9. + + The maximum number of nodes in segments that will be merged. The d= efault value changed to Integer.MAX_VALUE in JCR version= 1.9. + - merge-factor + + merge-factor + - 10 + + 10 + - Determines how often segment indices are merged. + + Determines how often segment indices are merged. + - max-field-length + + max-field-length + - 10000 + + 10000 + - The number of words that are fulltext indexed at most per property. + + The number of words that are fulltext indexed at most per property. + - cache-size + + cache-size + - 1000 + + 1000 + - Size of the document number cache. This cache maps uuids to lucene = document numbers + + Size of the document number cache. This cache maps uuids to lucene= document numbers + - force-consistencycheck + + force-consistencycheck + - false + + false + - Runs a consistency check on every startup. If false, a consistency = check is only performed when the search index detects a prior forced shutdo= wn. + + Runs a consistency check on every startup. If false, a consistency= check is only performed when the search index detects a prior forced shutd= own. + - auto-repair + + auto-repair + - true + + true + - Errors detected by a consistency check are automatically repaired. = If false, errors are only written to the log. + + Errors detected by a consistency check are automatically repaired.= If false, errors are only written to the log. + - document-order + + document-order + - true + + true + - If true and the query does not contain an 'order by' clause, result= nodes will be in document order. For better performance set to 'false' whe= n queries return many nodes. + + If true and the query does not contain an 'order by' clause, resul= t nodes will be in document order. For better performance set to 'false' wh= en queries return many nodes. + - result-fetch-size + + result-fetch-size + - Integer.MAX_VALUE + + Integer.MAX_VALUE + - The number of results when a query is executed. Default value: Integer.MAX_VALUE. + + The number of results when a query is executed. Default value: Integer.MAX_VALUE. + - excerptprovider-class + + excerptprovider-class + - DefaultXMLExcerpt + + DefaultXMLExcerpt + - The name of the class that implements $lucene.ExcerptProvi= der. This should be used for the rep:excerpt()= function in a query. + + The name of the class that implements org.exoplatform.ser= vices.jcr.impl.core. +query.lucene.ExcerptProvider. = + + + This should be used for the rep:excerpt() funct= ion in a query. + - support-highlighting + + support-highlighting + - false + + false + - If set to true additional information is stored in the index to sup= port highlighting using the rep:excerpt() function. + + If set to true additional information is stored in the index to su= pport highlighting using the rep:excerpt() function. + - synonymprovider-class + + synonymprovider-class + - none + + none + - The name of a class that implements $lucene.SynonymProvide= r. The default value is null. + + The name of a class that implements org.exoplatform.servi= ces.jcr.impl.core. +query.lucene.SynonymProvider. + + + The default value is null. + - synonymprovider-config-path + + synonymprovider-config-path + - none + + none + - The path to the synonym provider configuration file. This path is i= nterpreted relative to the path parameter. If there is a path element insid= e the SearchIndex element, then this path is interpreted= relative to the root path of the path. Whether this parameter is mandatory= depends on the synonym provider implementation. The default value is null. + + The path to the synonym provider configuration file. This path is = interpreted relative to the path parameter. If there is a path element insi= de the SearchIndex element, then this path is interprete= d relative to the root path of the path. Whether this parameter is mandator= y depends on the synonym provider implementation. The default value is null. + - indexing-configuration-path + + indexing-configuration-path + - none + + none + - The path to the indexing configuration file. + + The path to the indexing configuration file. + - indexing-configuration-class + + indexing-configuration-class + - IndexingConfigurationImpl + + IndexingConfigurationImpl + - The name of the class that implements $lucene.IndexingConf= iguration. + + The name of the class that implements org.exoplatform.ser= vices.jcr.impl.core. +query.lucene.IndexingConfiguration. + - force-consistencycheck + + force-consistencycheck + - false + + false + - If set to true a consistency check is performed depending on the pa= rameter forceConsistencyCheck. If set to false no consis= tency check is performed on startup, even if a redo log had been applied. + + If set to true a consistency check is performed depending on the p= arameter forceConsistencyCheck. If set to false no consi= stency check is performed on startup, even if a redo log had been applied. + - spellchecker-class + + spellchecker-class + - none + + none + - The name of a class that implements $lucene.SpellChecker. + + The name of a class that implements org.exoplatform.servi= ces.jcr.impl.core. +query.lucene.SpellChecker. + - errorlog-size + + errorlog-size + - 50(Kb) + + 50(Kb) + - The default size of error log file in Kb. + + The default size of error log file in Kb. + - upgrade-index + + upgrade-index + - false + + false + @@ -411,13 +556,20 @@ --> - analyzer + + analyzer + - org.apache.lucene.analysis.standard.StandardAnalyzer + + org.apache.lucene.analysis. + standard.StandardAnalyzer + - Class name of a lucene analyzer to use for fulltext indexing of tex= t. + + Class name of a lucene analyzer to use for fulltext indexing of te= xt. + + + Additionally, JBossIDMOrganizationServiceImpl use= s those defaults to perform identity management operations Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2010-05-24 02:58:= 11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2010-05-24 05:29:= 09 UTC (rev 3182) @@ -815,7 +815,7 @@ - Repeat the above process for the "gatein" realm user privileges. + Repeat the above process for the 'gatein' realm. = @@ -836,7 +836,7 @@ - Edit the jboss-as/server/<SERVER-TYPE>/gatein.ear/M= ETA-INF/gatein-jboss-beans.xml and uncomment this section: + Edit the jboss-as/server/<SERVER-TYPE>/deploy/gatei= n.ear/META-INF/gatein-jboss-beans.xml and uncomment this section: @@ -921,7 +921,7 @@ = = = = LOGIN_URL = = - http://localhost:8888/opensso/UI/Login?realm=3Dgatein&go= to=3Dhttp://localhost:8080 + http://localhost:8888/opensso/UI/Login?realm=3Dgatein&am= p;goto=3Dhttp://localhost:8080 /portal/private/classic = = @@ -1016,7 +1016,7 @@ SPNEGO Configuration - Activate the Host authentication. Add the following host login modul= e to the conf.xml or login-config.xml file (whichever your system uses): + Activate the Host authentication. Add the following host login modul= e to the jboss-as/server/<SERVER-TYPE>/conf/login-config.xm= l: @@ -1033,7 +1033,7 @@ ]]> - The 'keyTab' value should point to the keytab f= ile that was generated by the kadmin Kerberos tool. See = the Setting up your Kerberos Development Environment= guide for more details. + The 'keyTab' value should point to the keytab f= ile that was generated by the kadmin Kerberos tool. See = the Setting up your Kerberos Development Envi= ronment guide for more details. @@ -1073,7 +1073,7 @@ - Add the JBoss Negotiation binary by copying $GATEIN_SSO_HO= ME/spnego/jboss-negotiation-2.0.3.GA.jar to lib. DOC TODO <--= Which directory is meant by 'lib'?? (deploy/gatein.ear/lib?) + Add the JBoss Negotiation binary by copying $GATEIN_SSO_HO= ME/spnego/jboss-negotiation-2.0.3.GA.jar to jboss-as/s= erver/<SERVER-TYPE>/lib. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml 2010-05-24 = 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml 2010-05-24 = 05:29:09 UTC (rev 3182) @@ -14,12 +14,12 @@ An example would hosting the portal from http:/= /www.sample.com and the gadgets from htt= p://www.samplemodules.com. - To do this, configure a parameter called gadgets.hostName. The value is the path/to/gadgetServer in GadgetRegisteryService: + To do this, configure the gadgets.hostName paramet= er in the server/$CONF/deploy/gatein.ear/02portal.war/WEB-INF/con= f/portal/application-registry-configuration.xml file. The value = is the path/to/gadgetServer in = GadgetRegisteryService: = org.exoplatform.application.gadget.GadgetRegistryService - org.exoplatform.application.gadget.jcr.GadgetRegistryServiceImpl + org.exoplatform.application.gadget.impl.GadgetRegistryServiceImpl<= /type> gadgets.hostName Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConf= iguration.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurat= ion.xml 2010-05-24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurat= ion.xml 2010-05-24 05:29:09 UTC (rev 3182) @@ -232,6 +232,9 @@ The file eXoGadgets.war/WEB-INF/gadget.xml defines= the gadgets that will be available on a user dashboard. + + The example below shows a dashboard with all of the default gadgets inc= luded, as well as an extra currency converter gadget sourced from Google G= adgets. + Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfigu= ration.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration= .xml 2010-05-24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration= .xml 2010-05-24 05:29:09 UTC (rev 3182) @@ -287,8 +287,12 @@ javax.portlet.keywords=3DBreadcrumbs, Breadcrumb]]> = + = = Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuratio= n.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml = 2010-05-24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml = 2010-05-24 05:29:09 UTC (rev 3182) @@ -330,16 +330,14 @@ You must also define the following init params i= n your portlet.xml. = - - - javax.portlet.faces.autoDispatchEvents - true - - - javax.portlet.faces.bridgeEventHandler - org.foo.eventhandler - + + javax.portlet.faces.autoDispatchEvents + true + + + javax.portlet.faces.bridgeEventHandler + org.foo.eventhandler + ]]> While future versions on the 2.0 bridge will automate the dispatching= and consuming of events, at the moments you must dispatch the event in the= JSF or Seam backing bean. Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortletDevelopment/Standard.xml 2010-05-24 02:58:11= UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/PortletDevelopment/Standard.xml 2010-05-24 05:29:09= UTC (rev 3182) @@ -127,7 +127,7 @@ This section describes how to deploy a portlet in &PRODUCT;. - An example portlet called SimplestHelloWorld is l= ocated in the epp-doc/examples/portlets directory at the= root of your &PRODUCT; sources package. + An example portlet called SimplestHelloWorld is a= vailable in the /jboss-epp-5.0-src/portal/examples/portlets/ directory of the &PRODUCT; sources package or the boss-epp= -5.0-docs/epp-doc/examples/portlets directory of the documentati= on package..
Compiling @@ -161,6 +161,11 @@ + Add the new portlet to the Application Registry. + + + + Create a new portal page and add the portlet to it. = @@ -228,7 +233,7 @@
Portlet Class - Below is the Java source for an example portlet named Simpl= estHelloWorldPortlet/src/main/java/org/gatein/portal/examples/portlets/Simp= lestHelloWorldPortlet.java : + Below is the Java source for an example portlet named simpl= esthelloworld/src/main/java/org/jboss/portal/portlet/samples: @@ -239,25 +244,25 @@ = - +} +]]> @@ -327,7 +332,7 @@ SimplestHelloWorldPortlet - org.gatein.portal.examples.portlets.SimplestHelloWorldPortlet + org.jboss.portal.portlet.samples.SimplestHelloWorldPortlet text/html @@ -405,7 +410,8 @@ Compiling the example - The example used in this section can be found in the epp-do= c/examples/portlets directory at the root of your &PRODUCT; sourc= es package. + The example used in this section is available in the /jbos= s-epp-5.0-src/portal/examples/portlets/ directory of the &PRODUC= T; sources package or the boss-epp-5.0-docs/epp-doc/examples/port= lets directory of the documentation package. + @@ -427,6 +433,12 @@ Copy jsphellouser/target/gatein-jsp-hellouser-1.0.0-GA-SNAPSHOT.war to the deploy directory of JBoss Application Server. + + + Add the new portlet to the Application Registry. + + + Create a new portal page and add the portlet to it. @@ -441,11 +453,12 @@ = +
Package Structure @@ -602,7 +615,7 @@ - processAction is the method from Gerne= ricPorlet to override for the action phase. + processAction is the method from Gener= icPorlet to override for the action phase. @@ -737,7 +750,7 @@ In order to write a portlet using JSF a 'bridge' is needed. This soft= ware allows developers to write a portlet application as if it was a JSF ap= plication. The bridge then negotiates the interactions between the two laye= rs. - An example using the JBoss Portlet Bridge is available in the epp-doc/examples/portlets directory at the root of your &PRODUC= T; sources package. The configuration is slightly different from a JSP appl= ication. This example can be used as a base to configure instead of creatin= g a new application. + An example using the JBoss Portlet Bridge is available in the /jboss-epp-5.0-src/portal/examples/portlets/ directory of the= &PRODUCT; sources package or the /jboss-epp-5.0-docs/epp-doc/exa= mples/portlets directory of the documentation package. The confi= guration is slightly different from a JSP application. This example can be = used as a base to configure instead of creating a new application. As in any JSF application, the file faces-config.xml is required. It must contain the following information: Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_= Reference_Guide/en-US/modules/WSRP.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/WSRP.xml 2010-05-24 02:58:11 UTC (rev 3181) +++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere= nce_Guide/en-US/modules/WSRP.xml 2010-05-24 05:29:09 UTC (rev 3182) @@ -344,7 +344,7 @@ - Log into the portal as an administrator and go to the Application= Registry (Click here if using the default installation)= . = + Log into the portal as an administrator and go to the Application= Registry (Click http://localhost:8080/portal/private/classic/admi= nistration/registry if using the default installation). = --===============7384857987569668955==--