November 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3305) Automatically deploy portal data when it has never been initiated

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3305?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3305: ---------------------------------------- Description: Case to study in eXo Platform - Start eXo Platform server - Stop server then install acme extension - Start eXo Platform again - Check if acme extension is deployed. was: Case to study in eXo Platform - Start eXo Platform server - Stop server then install acme extension - Start eXo Platform again - Check if acme extension is deployed. In Gatein, you can check by deploying new extension. > Automatically deploy portal data when it has never been initiated > ----------------------------------------------------------------- > > Key: GTNPORTAL-3305 > URL: https://issues.jboss.org/browse/GTNPORTAL-3305 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.7.Final > Reporter: Tran Trung Thanh > Priority: Minor > > Case to study in eXo Platform > - Start eXo Platform server > - Stop server then install acme extension > - Start eXo Platform again > - Check if acme extension is deployed. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3305) Automatically deploy portal data when it has never been initiated

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3305?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3305: ---------------------------------------- Summary: Automatically deploy portal data when it has never been initiated (was: Automatically deploy portal data when it has never initiated) > Automatically deploy portal data when it has never been initiated > ----------------------------------------------------------------- > > Key: GTNPORTAL-3305 > URL: https://issues.jboss.org/browse/GTNPORTAL-3305 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.7.Final > Reporter: Tran Trung Thanh > Priority: Minor > > Case to study in eXo Platform > - Start eXo Platform server > - Stop server then install acme extension > - Start eXo Platform again > - Check if acme extension is deployed. > In Gatein, you can check by deploying new extension. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3305) Automatically deploy portal data when it has never initiated

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3305?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3305: ---------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/706 > Automatically deploy portal data when it has never initiated > ------------------------------------------------------------ > > Key: GTNPORTAL-3305 > URL: https://issues.jboss.org/browse/GTNPORTAL-3305 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.7.Final > Reporter: Tran Trung Thanh > Priority: Minor > > Case to study in eXo Platform > - Start eXo Platform server > - Stop server then install acme extension > - Start eXo Platform again > - Check if acme extension is deployed. > In Gatein, you can check by deploying new extension. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3305) Automatically deploy portal data when it has never initiated

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-3305: ------------------------------------------- Summary: Automatically deploy portal data when it has never initiated Key: GTNPORTAL-3305 URL: https://issues.jboss.org/browse/GTNPORTAL-3305 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.5.7.Final Reporter: Tran Trung Thanh Priority: Minor Case to study in eXo Platform - Start eXo Platform server - Stop server then install acme extension - Start eXo Platform again - Check if acme extension is deployed. In Gatein, you can check by deploying new extension. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3295) Incorrect position of inputs in Edit Portlet dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3295?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3295: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 794165|https://bugzilla.redhat.com/show_bug.cgi?id=794165] from POST to MODIFIED > Incorrect position of inputs in Edit Portlet dialog > --------------------------------------------------- > > Key: GTNPORTAL-3295 > URL: https://issues.jboss.org/browse/GTNPORTAL-3295 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.6.4.Final, 3.7.0.Final > > > The scope of the present issue is only LogoPortlet. IFramePortlet mentioned in the original report https://bugzilla.redhat.com/show_bug.cgi?id=794165 works correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3281) On GateIn shutdown: WARN [exo.jcr.component.core.RepositoryImpl] Repository repository is OFFLINE

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3281?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3281: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.6.4.Final Resolution: Done > On GateIn shutdown: WARN [exo.jcr.component.core.RepositoryImpl] Repository repository is OFFLINE > -------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3281 > URL: https://issues.jboss.org/browse/GTNPORTAL-3281 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WSRP integration > Reporter: Peter Palaga > Assignee: Juraci Paixão Kröhling > Fix For: 3.6.4.Final, 3.7.0.Final > > > The above Warning is logged during GateIn shutdown. There should be no warnings in an out of the box instance of GateIn. > The stack during the warning is as follows: > {code} > Thread [Thread-68] (Suspended (breakpoint at line 155 in LocationAwareSLF4JExoLog)) > LocationAwareSLF4JExoLog.warn(Object) line: 155 > RepositoryImpl.getSystemSession(String) line: 400 > RepositoryImpl.getSystemSession(String) line: 81 > SessionProvider.getSession(String, ManageableRepository) line: 202 > JCRPersister$WSRPSessionLifeCycle(JCRPersister$AbstractSessionLifeCycle).login() line: 82 > ChromatticImpl.openSession() line: 58 > JCRPersister(BaseChromatticPersister).getSession() line: 109 > JCRProducerConfigurationService.getPersistedLastModifiedForConfiguration() line: 128 > JCRProducerConfigurationService(AbstractProducerConfigurationService).getConfiguration() line: 48 > WSRPProducerImpl.getProducerConfiguration() line: 346 > WSRPProducerImpl.getProducerRegistrationRequirements() line: 193 > WSRPProducerImpl.stop() line: 417 > WSRPServiceIntegration.stopProducer() line: 381 > WSRPServiceIntegration.stop() line: 375 > GeneratedMethodAccessor121.invoke(Object, Object[]) line: not available > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 606 > LifecycleVisitor.traverse(Container) line: 98 > LifecycleVisitor.stop(Container) line: 166 > ConcurrentContainer.stop() line: 463 > CachingContainer(AbstractContainer).stop() line: 75 > ManageableContainer(AbstractContainer).stop() line: 75 > ManageableContainer.stop() line: 240 > PortalContainer(AbstractContainer).stop() line: 75 > PortalContainer(ExoContainer).stop() line: 273 > PortalContainer.stop() line: 689 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 606 > LifecycleVisitor.traverse(Container) line: 98 > LifecycleVisitor.stop(Container) line: 166 > ConcurrentContainer.stop() line: 463 > CachingContainer(AbstractContainer).stop() line: 75 > ManageableContainer(AbstractContainer).stop() line: 75 > ManageableContainer.stop() line: 240 > RootContainer(AbstractContainer).stop() line: 75 > RootContainer(ExoContainer).stop() line: 273 > RootContainer.stop() line: 1230 > RootContainer$ShutdownThread$1.run() line: 1220 > RootContainer$ShutdownThread$1.run() line: 1217 > SecurityHelper.doPrivilegedAction(PrivilegedAction<E>) line: 290 > RootContainer$ShutdownThread.run() line: 1216 > {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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3295) Incorrect position of inputs in Edit Portlet dialog

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3295?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3295: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Incorrect position of inputs in Edit Portlet dialog > --------------------------------------------------- > > Key: GTNPORTAL-3295 > URL: https://issues.jboss.org/browse/GTNPORTAL-3295 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.6.4.Final, 3.7.0.Final > > > The scope of the present issue is only LogoPortlet. IFramePortlet mentioned in the original report https://bugzilla.redhat.com/show_bug.cgi?id=794165 works correctly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2072) NoSuchDataException is thrown after importing pages through export/import tool.

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2072?page=com.atlassian.jira.pl... ] Nick Scavelli commented on GTNPORTAL-2072: ------------------------------------------ With WRT to the PR here https://github.com/gatein/gatein-portal/pull/687 I'm still seeing the issue. If you export the admin site, import the admin site w/ overwrite, refresh page you should see an issue. > NoSuchDataException is thrown after importing pages through export/import tool. > ------------------------------------------------------------------------------- > > Key: GTNPORTAL-2072 > URL: https://issues.jboss.org/browse/GTNPORTAL-2072 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.2.0-Beta01 > Reporter: Nick Scavelli > Assignee: Vu Viet Phuong > Labels: import > Original Estimate: 1 day > Time Spent: 1 day, 2 hours > Remaining Estimate: 0 minutes > > Below exception is thrown after importing pages through management tools (see steps to reproduce section). I think this is a stale storageId coming from the UI when the data has changed outside the UI. Typically logging out solves the issue, but this isn't optimal. Changes to data should not be only achievable through the UI. The changes are being sent through DataStorage, so there should be someway to sync this data up. > Stacktrace: > {noformat} > Caused by: org.exoplatform.portal.config.NoSuchDataException: Can not find 1c42bec77f0000011076449207f5d085 > at org.exoplatform.portal.pom.config.POMSession.findCustomizationById(POMSession.java:214) > at org.exoplatform.portal.pom.config.tasks.PreferencesTask$Load.run(PreferencesTask.java:91) > at org.exoplatform.portal.pom.config.POMSession.execute(POMSession.java:405) > at org.exoplatform.portal.pom.config.ExecutorDispatcher.execute(ExecutorDispatcher.java:60) > at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38) > at org.exoplatform.portal.pom.config.cache.DataCache.read(DataCache.java:169) > at org.exoplatform.portal.pom.config.cache.DataCache.execute(DataCache.java:61) > at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38) > at org.exoplatform.portal.pom.config.cache.PortalNamesCache.execute(PortalNamesCache.java:77) > at org.exoplatform.portal.pom.config.POMSessionManager.execute(POMSessionManager.java:251) > at org.exoplatform.portal.pom.config.POMDataStorage.load(POMDataStorage.java:176) > at org.exoplatform.portal.config.DataStorageImpl.load(DataStorageImpl.java:111) > at org.exoplatform.portal.webui.application.ModelAdapter$1.getPortletContext(ModelAdapter.java:89) > at org.exoplatform.portal.webui.application.UIPortlet.getPortletContext(UIPortlet.java:993) > at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:829) > at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:212) > {noformat} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3293) Group all mobile responsive portets into a war packaging

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3293?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3293: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Group all mobile responsive portets into a war packaging > -------------------------------------------------------- > > Key: GTNPORTAL-3293 > URL: https://issues.jboss.org/browse/GTNPORTAL-3293 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Packaging > Affects Versions: 3.6.3.Final > Reporter: Trong Tran > Assignee: Vu Viet Phuong > Labels: backlogs, plan_3.7.0 > Fix For: 3.7.0.Final > > Original Estimate: 1 day, 4 hours > Time Spent: 1 day, 3 hours > Remaining Estimate: 0 minutes > > Make these portlets https://github.com/gatein/gatein-portal/tree/master/mobile-integration/po... grouped in a war > P/S: Don't forget to test both JBoss and Tomcat bundles -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3198) Update documentation

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3198?page=com.atlassian.jira.pl... ] Vu Viet Phuong resolved GTNPORTAL-3198. --------------------------------------- Resolution: Done > Update documentation > -------------------- > > Key: GTNPORTAL-3198 > URL: https://issues.jboss.org/browse/GTNPORTAL-3198 > Project: GateIn Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Vu Viet Phuong > Labels: backlogs, plan_3.7.0 > Fix For: 3.7.0.Final > > Attachments: public-upload-restriction > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > The central doc is https://docs.jboss.org/author/display/GTNPORTALDOC/Home -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues November 2013