February 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Racha Touzi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Racha Touzi updated GTNPORTAL-3404: ----------------------------------- Description: The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . But in local mode we don't really need the transport configuration and the clustering configuration {code} <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" xmlns="urn:infinispan:config:5.2"> <global> <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory"> <properties> <property name="threadNamePrefix" value="EvictionThread"/> </properties> </evictionScheduledExecutor> <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/> <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000"> <properties> <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/> </properties> </transport> </global> <default> <clustering mode="replication"> <stateTransfer timeout="20000" fetchInMemoryState="false" /> <sync replTimeout="20000"/> </clustering> <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/> <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/> <jmxStatistics enabled="true"/> <eviction strategy="NONE"/> <loaders passivation="false" shared="false" preload="false"> <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> <async enabled="false"/> </loader> </loaders> </default> </infinispan> {code} So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , the path must be {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml {code} instead of {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml {code} was: The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . The configuration of JCR Index cache must be one for local mode and one for Cluster mode , So the path must be {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml {code} instead of {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml {code} > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Racha Touzi > Priority: Minor > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > <infinispan > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > <global> > <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory"> > <properties> > <property name="threadNamePrefix" value="EvictionThread"/> > </properties> > </evictionScheduledExecutor> > <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/> > <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000"> > <properties> > <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/> > </properties> > </transport> > </global> > <default> > <clustering mode="replication"> > <stateTransfer timeout="20000" fetchInMemoryState="false" /> > <sync replTimeout="20000"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/> > <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/> > <jmxStatistics enabled="true"/> > <eviction strategy="NONE"/> > <loaders passivation="false" shared="false" preload="false"> > <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> > <async enabled="false"/> > </loader> > </loaders> > </default> > </infinispan> > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Racha Touzi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Racha Touzi updated GTNPORTAL-3404: ----------------------------------- Affects Version/s: 3.7.0.Final > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Priority: Minor > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > <infinispan > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > <global> > <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory"> > <properties> > <property name="threadNamePrefix" value="EvictionThread"/> > </properties> > </evictionScheduledExecutor> > <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/> > <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000"> > <properties> > <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/> > </properties> > </transport> > </global> > <default> > <clustering mode="replication"> > <stateTransfer timeout="20000" fetchInMemoryState="false" /> > <sync replTimeout="20000"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/> > <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/> > <jmxStatistics enabled="true"/> > <eviction strategy="NONE"/> > <loaders passivation="false" shared="false" preload="false"> > <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> > <async enabled="false"/> > </loader> > </loaders> > </default> > </infinispan> > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3405) Problem when edit portal config.

by Racha Touzi (JIRA)

Racha Touzi created GTNPORTAL-3405: -------------------------------------- Summary: Problem when edit portal config. Key: GTNPORTAL-3405 URL: https://issues.jboss.org/browse/GTNPORTAL-3405 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.7.0.Final Reporter: Racha Touzi -Create a new page "Sites Management" contains the portlet "Portal Navigation Portlet" under "Administration" menu . Click on Group Editor -> Edit Layout Click on "Properties" Change somethings: label, description or locate ( ex: change label: test). Click Save ==> The label is not updated under the menu "Site "=> NOk Go to Administration-> Sites Management click on "Edit site configuration" => Label of classic portal is not updated => NOK. Expected output: new label is updated in Edit Site's Configuration and the menu "Site" PS: the problem is reproduced only when edit the site properties when we are in the group navigation . for example This problem is not reproduced when edit the site properties when we are in the home page . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Racha Touzi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Racha Touzi updated GTNPORTAL-3404: ----------------------------------- Security Sensitive Issue: (was: Check in case of security relevant issue) > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Racha Touzi > Priority: Minor > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > So the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Racha Touzi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Racha Touzi updated GTNPORTAL-3404: ----------------------------------- Security Sensitive Issue: Check in case of security relevant issue > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Racha Touzi > Priority: Minor > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > So the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Racha Touzi (JIRA)

Racha Touzi created GTNPORTAL-3404: -------------------------------------- Summary: The path of JCr index cache is hard coded in configuration.properties Key: GTNPORTAL-3404 URL: https://issues.jboss.org/browse/GTNPORTAL-3404 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Racha Touzi Priority: Minor The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . The configuration of JCR Index cache must be one for local mode and one for Cluster mode , So the path must be {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml {code} instead of {code} gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3403) Custom validator of page node name

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3403?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3403: ---------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/793 Fix description: - Implement new ConfigurableIdentifierValidator > Custom validator of page node name > ---------------------------------- > > Key: GTNPORTAL-3403 > URL: https://issues.jboss.org/browse/GTNPORTAL-3403 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Tran Trung Thanh > > Please provide a way to customize page name pattern. In current code, it is hardcoded. for example: https://github.com/gatein/gatein-portal/blob/3.5.x/portlet/exoadmin/src/m... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3403) Custom validator of page node name

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-3403: ------------------------------------------- Summary: Custom validator of page node name Key: GTNPORTAL-3403 URL: https://issues.jboss.org/browse/GTNPORTAL-3403 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.5.8.Final Reporter: Tran Trung Thanh Please provide a way to customize page name pattern. In current code, it is hardcoded. for example: https://github.com/gatein/gatein-portal/blob/3.5.x/portlet/exoadmin/src/m... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNMOP-51) Upgrade to Chromattic 1.3.0-beta2

by Julien Viet (JIRA)

Julien Viet created GTNMOP-51: --------------------------------- Summary: Upgrade to Chromattic 1.3.0-beta2 Key: GTNMOP-51 URL: https://issues.jboss.org/browse/GTNMOP-51 Project: GateIn Model Object for Portal Issue Type: Feature Request Reporter: Julien Viet Assignee: Julien Viet Fix For: 1.3.0.Beta02 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3402: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=973835 > Allow customers to customize login validation and accounts expiration > ---------------------------------------------------------------------- > > Key: GTNPORTAL-3402 > URL: https://issues.jboss.org/browse/GTNPORTAL-3402 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > Allow customers to add custom password rules to their GateIn installations. > We've had a discussion about the possibilities, and it seems that the best for now would be something as follows: > 1) Adapt/extend the current UserConfigurableValidator, which allows the usage of min/max/regex constraints for values based on values from a configuration file, for instance: > gatein.validators.mycompanypasspolicy.length.min=5 > gatein.validators.mycompanypasspolicy.length.max=50 > gatein.validators.mycompanypasspolicy.regexp=... > 2) Extend the User Interface to allow the administrator to enter the name of the configuration entry related to the password policy (mycompanypasspolicy , in this case). > (originally requested via Bugzilla #973835) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues February 2014