[JBoss JIRA] Created: (GTNPORTAL-702) Remove "Import Applications" feature from Administration category menu
by Nicolas Martignole (JIRA)
Remove "Import Applications" feature from Administration category menu
-----------------------------------------------------------------------
Key: GTNPORTAL-702
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-702
Project: GateIn Portal
Issue Type: Feature Request
Components: User Interface
Affects Versions: 3.0.0-CR01
Reporter: Nicolas Martignole
Priority: Minor
GateIn Portal has an "Import Applications" submenu feature that is used to import applications the very first time GateIn is used. Julien Viet told me that this is related to the JCR.
I would suggest to remove this feature, that has to be manually triggered, and let the Portal adds any valid WAR package at startup-time. This would avoir the need to execute this task once for all.
When we compare with Liferay 5.2, any valid web application is automatically available in the "Control Panel" Menu. When an application is not valid, but some of its meta can be extracted, the Liferay control panel will show the Portlet name grayed out.
As a GateIn Portal user, I'd like to drop my WAR in the webapp folder, reload the list of available applications, and see all my Portlets, without the need to call this "Import Applications" feature.
Nicolas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-690) IllegalStateException when logout from GateIn portal with clustered setup
by Marek Posolda (JIRA)
IllegalStateException when logout from GateIn portal with clustered setup
-------------------------------------------------------------------------
Key: GTNPORTAL-690
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-690
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-CR01
Environment: Sun JDK 1.6,
GateIn-3.0.0-CR01 bundle with JBoss 5.1.0
Reporter: Marek Posolda
1) Edit server/default/conf/gatein/configuration.properties for clustered setup (file attached)
2) Run it with ./run.sh -Dexo.profiles=cluster
3) When login as root and then logout back I can see IllegalAccessException in server log.
I tried it also with GateIn deployed in "all" configuration and with GateIn deployed on EAP-5. I can see this exception in all setups I tried. Nothing seems to be broken, only the exception in server log is annoying:
java.lang.IllegalStateException: Cannot create a session after the response has been committed
at org.apache.catalina.connector.Request.doGetSession(Request.java:2338)
at org.apache.catalina.connector.Request.getSession(Request.java:2094)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:844)
at org.exoplatform.portal.application.replication.ReplicatingStateManager.getSession(ReplicatingStateManager.java:174)
at org.exoplatform.portal.application.replication.ReplicatingStateManager.storeUIRootComponent(ReplicatingStateManager.java:120)
at org.exoplatform.portal.application.PortalStateManager.storeUIRootComponent(PortalStateManager.java:59)
at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:115)
at org.exoplatform.web.WebAppController.service(WebAppController.java:143)
at org.exoplatform.portal.application.PortalController.onService(PortalController.java:127)
at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-503) javax.jcr.RepositoryException when same database used for both portal containers "portal" and "sample-portal"
by Marek Posolda (JIRA)
javax.jcr.RepositoryException when same database used for both portal containers "portal" and "sample-portal"
-------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-503
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-503
Project: GateIn Portal
Issue Type: Bug
Environment: Ubuntu linux,
Sun JDK 1.6,
EAP 5 with GateIn from trunk (revision 1252)
Reporter: Marek Posolda
Attachments: database-configuration.xml
When same database is used for both portal containers "portal" and "sample-portal" in database-configuration.xml, then you can see error in server log during GateIn startup. I've seeen this in server.log during GateIn startup:
16:00:07,014 ERROR [NodeIndexer] Binary value indexer error javax.jcr.RepositoryException: /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory): /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory)
javax.jcr.RepositoryException: /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory): /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory)
at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getItemByName(JDBCStorageConnection.java:804)
at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getItemData(JDBCStorageConnection.java:690)
at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.getItemData(WorkspacePersistentDataManager.java:599)
at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.getPersistedItemData(CacheableWorkspaceDataManager.java:519)
at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.getItemData(CacheableWorkspaceDataManager.java:297)
By default each container has different database because database-configuration.xml looks like this:
<property name="driverClassName" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb${container.name.suffix}"/>
<property name="username" value="sa"/>
<property name="password" value=""/>
Problem occurs when same DB is used for both containers, so URL looks like this:
<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb_shared"/>
I believe that it should be possible to use same DB for both portal containers without any exceptions in server.log. Right now, there is similar issue GTNPORTAL-474 , which addresses exceptions with picketlink idm. So I am using database-configuration.xml from attachement where DB is shared only for JCR and not for picketlink. And with this configuration, I am seeing only JCR exceptions.
My database-configuration is in attachement as well as my server.log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month