[JBoss JIRA] (GTNPORTAL-3263) "Restricted" page editor
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3263?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3263:
----------------------------------------------------
Jared MORGAN <jmorgan(a)redhat.com> changed the Status of [bug 1072181|https://bugzilla.redhat.com/show_bug.cgi?id=1072181] from ASSIGNED to VERIFIED
> "Restricted" page editor
> ------------------------
>
> Key: GTNPORTAL-3263
> URL: https://issues.jboss.org/browse/GTNPORTAL-3263
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> See https://community.jboss.org/wiki/RestrictedPageEditor
> A customer is willing to give the ability to many different users to edit pages. Those users would require a simplified page editor and be constrained to simple actions. In particular, users should not be able to compose complex pages and risk to break the layouts.
> The layouts should be restricted to what is available from the "Containers" tab of the editor.
> In particular the 2 following scenarios should not be possible:
> Scenario 1: User should not be able to put an application above/below the 2 column layout (As this break the pre-defined layouts, suddenly the user is able to have a single column representation while this may not have been provided):
> Scenario 2: User should not be able to put a layout within a layout (only above or below existing ones)
> Proposed solution
> Add an option in configuration.properties for a restricted page and layout editor. This would apply across the whole portal.
> gatein.portal.pageeditor.mode=full (default) | restricted
> gatein.portal.layouteditor.mode=full (default) | restricted
>
> Applications could only be added to predefined layouts (and not directly on a page).
> Containers could only be added to the root of a page (not inside another container).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (GTNPORTAL-3517) Cannot start Gatein Portal with MySQL in UTF-8
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3517?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3517:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Assignee: Trong Tran
Resolution: Done
> Cannot start Gatein Portal with MySQL in UTF-8
> ----------------------------------------------
>
> Key: GTNPORTAL-3517
> URL: https://issues.jboss.org/browse/GTNPORTAL-3517
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.10.Final
> Reporter: Tran Trung Thanh
> Assignee: Trong Tran
> Fix For: 3.9.0.Final
>
>
> If we want to use Gatein Portal in UTF-8 mode with MySQL, even if we configure the dialect to mysql-utf8, we get issues of type:
> {code}
> Caused by: org.jboss.cache.CacheException: Unable to start cache loaders
> at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:470) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> ... 81 common frames omitted
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.6.0_45]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) ~[na:1.6.0_45]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ~[na:1.6.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513) ~[na:1.6.0_45]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.Util.getInstance(Util.java:386) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4098) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4030) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2671) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1749) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1666) ~[mysql-connector-java-5.1.19.jar:na]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.jboss.cache.loader.AdjListJDBCCacheLoader.start(AdjListJDBCCacheLoader.java:300) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.loader.JDBCCacheLoader.start(JDBCCacheLoader.java:396) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.exoplatform.services.jcr.impl.core.lock.jbosscache.ControllerCacheLoader.start(ControllerCacheLoader.java:312) ~[exo.jcr.component.core-1.15.8-GA-SNAPSHOT.jar:1.15.8-GA-SNAPSHOT]
> at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:464) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> {code}
> NB: The db schema has been created using the next command:
> {code}
> CREATE DATABASE plf_jcr_utf8 DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_bin;
> {code}
> To make Gatein Portal work with MySQL in UTF-8, we need [JCR-2312|https://jira.exoplatform.org/browse/JCR-2312] and add new parameter introduced from JCR issue in the configuration of the lock manager which is infinispan-cl-cache.jdbc.dialect in case of infinispan and jbosscache-cl-cache.jdbc.dialect in case of JBC.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (GTNPORTAL-3517) Cannot start Gatein Portal with MySQL in UTF-8
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3517?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3517:
---------------------------------------
Fixed in master only
> Cannot start Gatein Portal with MySQL in UTF-8
> ----------------------------------------------
>
> Key: GTNPORTAL-3517
> URL: https://issues.jboss.org/browse/GTNPORTAL-3517
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.10.Final
> Reporter: Tran Trung Thanh
> Fix For: 3.9.0.Final
>
>
> If we want to use Gatein Portal in UTF-8 mode with MySQL, even if we configure the dialect to mysql-utf8, we get issues of type:
> {code}
> Caused by: org.jboss.cache.CacheException: Unable to start cache loaders
> at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:470) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> ... 81 common frames omitted
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.6.0_45]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) ~[na:1.6.0_45]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ~[na:1.6.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513) ~[na:1.6.0_45]
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.Util.getInstance(Util.java:386) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4098) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4030) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2671) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1749) ~[mysql-connector-java-5.1.19.jar:na]
> at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1666) ~[mysql-connector-java-5.1.19.jar:na]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42]
> at org.jboss.cache.loader.AdjListJDBCCacheLoader.start(AdjListJDBCCacheLoader.java:300) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.loader.JDBCCacheLoader.start(JDBCCacheLoader.java:396) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.exoplatform.services.jcr.impl.core.lock.jbosscache.ControllerCacheLoader.start(ControllerCacheLoader.java:312) ~[exo.jcr.component.core-1.15.8-GA-SNAPSHOT.jar:1.15.8-GA-SNAPSHOT]
> at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:464) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> {code}
> NB: The db schema has been created using the next command:
> {code}
> CREATE DATABASE plf_jcr_utf8 DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_bin;
> {code}
> To make Gatein Portal work with MySQL in UTF-8, we need [JCR-2312|https://jira.exoplatform.org/browse/JCR-2312] and add new parameter introduced from JCR issue in the configuration of the lock manager which is infinispan-cl-cache.jdbc.dialect in case of infinispan and jbosscache-cl-cache.jdbc.dialect in case of JBC.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (GTNPORTAL-3529) Enhance UI container layout fully extensible and customizable
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3529?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3529:
---------------------------------------
Added documentation at https://docs.jboss.org/author/display/GTNPORTAL39/Custom+UI+Container+layout
> Enhance UI container layout fully extensible and customizable
> -------------------------------------------------------------
>
> Key: GTNPORTAL-3529
> URL: https://issues.jboss.org/browse/GTNPORTAL-3529
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.8.2.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
> Fix For: 3.9.0.Final
>
>
> In PortalDataMapper, we have this
> {code}
> if (UITabContainer.TAB_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UITabContainer.class, null, null);
> } else if (UIColumnContainer.COLUMN_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UIColumnContainer.class, null, null);
> } else {
> ...
> {code}
> - This should be improved by making it more flexible, and extensible. Using ServiceLoader to load the factories class that help to create UIContainer by their factory-id
> - The proposed solution is: using factory-id attribute of container model to create corresponding UI container type. And the creation task is delegated to a factory service, that can be loaded via service loader. This design make gatein ui container creation more flexible, it's easy to deploy gatein extension which define a new UI container type with new factory-id
> - factory-id has already be used before in gatein, we use it to create UITabContainer, UIColumnContainer... This issue will add interface for factory service: UIComponentFactory and a default implementation for create current gatein build-in container: DefaultUIContainerFactory. It's declared as a service load by java ServiceLoader
> - When gatein try to create UI container (from model loaded from database or from xml config file). ServiceLoader will load registered UIComponentFactory services, then delegate creation task with factory-id as argument
> - A developer can deploy a jar that declare a new ui factory service, then help to create a new type of UI container easily
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (GTNPORTAL-3529) Enhance UI container layout fully extensible and customizable
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3529?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3529:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Enhance UI container layout fully extensible and customizable
> -------------------------------------------------------------
>
> Key: GTNPORTAL-3529
> URL: https://issues.jboss.org/browse/GTNPORTAL-3529
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.8.2.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
> Fix For: 3.9.0.Final
>
>
> In PortalDataMapper, we have this
> {code}
> if (UITabContainer.TAB_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UITabContainer.class, null, null);
> } else if (UIColumnContainer.COLUMN_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UIColumnContainer.class, null, null);
> } else {
> ...
> {code}
> - This should be improved by making it more flexible, and extensible. Using ServiceLoader to load the factories class that help to create UIContainer by their factory-id
> - The proposed solution is: using factory-id attribute of container model to create corresponding UI container type. And the creation task is delegated to a factory service, that can be loaded via service loader. This design make gatein ui container creation more flexible, it's easy to deploy gatein extension which define a new UI container type with new factory-id
> - factory-id has already be used before in gatein, we use it to create UITabContainer, UIColumnContainer... This issue will add interface for factory service: UIComponentFactory and a default implementation for create current gatein build-in container: DefaultUIContainerFactory. It's declared as a service load by java ServiceLoader
> - When gatein try to create UI container (from model loaded from database or from xml config file). ServiceLoader will load registered UIComponentFactory services, then delegate creation task with factory-id as argument
> - A developer can deploy a jar that declare a new ui factory service, then help to create a new type of UI container easily
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months
[JBoss JIRA] (GTNPORTAL-3529) Enhance UI container layout fully extensible and customizable
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3529?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3529:
----------------------------------
Summary: Enhance UI container layout fully extensible and customizable (was: Make UIContainer creation more flexible)
> Enhance UI container layout fully extensible and customizable
> -------------------------------------------------------------
>
> Key: GTNPORTAL-3529
> URL: https://issues.jboss.org/browse/GTNPORTAL-3529
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.8.2.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
> Fix For: 3.9.0.Final
>
>
> In PortalDataMapper, we have this
> {code}
> if (UITabContainer.TAB_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UITabContainer.class, null, null);
> } else if (UIColumnContainer.COLUMN_CONTAINER.equals(container.getFactoryId())) {
> uiTempContainer = uiContainer.createUIComponent(context, UIColumnContainer.class, null, null);
> } else {
> ...
> {code}
> - This should be improved by making it more flexible, and extensible. Using ServiceLoader to load the factories class that help to create UIContainer by their factory-id
> - The proposed solution is: using factory-id attribute of container model to create corresponding UI container type. And the creation task is delegated to a factory service, that can be loaded via service loader. This design make gatein ui container creation more flexible, it's easy to deploy gatein extension which define a new UI container type with new factory-id
> - factory-id has already be used before in gatein, we use it to create UITabContainer, UIColumnContainer... This issue will add interface for factory service: UIComponentFactory and a default implementation for create current gatein build-in container: DefaultUIContainerFactory. It's declared as a service load by java ServiceLoader
> - When gatein try to create UI container (from model loaded from database or from xml config file). ServiceLoader will load registered UIComponentFactory services, then delegate creation task with factory-id as argument
> - A developer can deploy a jar that declare a new ui factory service, then help to create a new type of UI container easily
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 2 months