[JBoss JIRA] (GTNPORTAL-3317) WARN Cannot load and merge the bundle: locale.portal.extension
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3317:
---------------------------------------
Summary: WARN Cannot load and merge the bundle: locale.portal.extension
Key: GTNPORTAL-3317
URL: https://issues.jboss.org/browse/GTNPORTAL-3317
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Peter Palaga
Assignee: Peter Palaga
When Sample Portal and Portal Extension from Quickstarts are deployed, the following two warnings occur in the server log:
{code}
WARN Cannot load and merge the bundle: locale.portal.extension
...
WARN Cannot load and merge the bundle: locale.portal.sample
{code}
But the localized strings strings seem to work.
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-3315) Portal setup improvements
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3315?page=com.atlassian.jira.pl... ]
Vu Viet Phuong updated GTNPORTAL-3315:
--------------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
> Portal setup improvements
> --------------------------
>
> Key: GTNPORTAL-3315
> URL: https://issues.jboss.org/browse/GTNPORTAL-3315
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Hai Nguyen
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
> Today there is a need that it could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
> - Ability to Enable/Disable the feature
> - Make it work more as an extension, to not forced adding things to core portal
> - Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
> - Removing repository/workspace name hard-coding in PortalSetupService
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-2751) <priority> in navigation.xml files ignored for merge importMode
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2751?page=com.atlassian.jira.pl... ]
Vu Viet Phuong updated GTNPORTAL-2751:
--------------------------------------
Remaining Estimate: 1 day (was: 1 hour)
> <priority> in navigation.xml files ignored for merge importMode
> ----------------------------------------------------------------
>
> Key: GTNPORTAL-2751
> URL: https://issues.jboss.org/browse/GTNPORTAL-2751
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Trong Tran
> Original Estimate: 4 hours
> Time Spent: 1 day, 2 hours
> Remaining Estimate: 1 day
>
> Steps to reproduce:
> Clone the Portal Extension Quickstart and deploy it changing the {{<priority>}} value in {{war/src/main/webapp/WEB-INF/conf/sample-ext/portal/group/platform/administrators/navigation.xml}}.
> NOT OK: The changes have no effect, because priority is ignored in {{org.exoplatform.portal.mop.importer.NavigationImporter.perform()}} with {{importMode}} {{merge}}.
> h3. Solution Proposal A
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Explicitly state in the documentation [1] that {{<priority>}} is considered only if not already set (first wins).
> h3. Solution Proposal B
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Change the behavior of {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}} to the effect that {{<priority>}} is handled in the same way as navigation nodes: it is used or ignored according to the chosen {{importMode}}. Esp. for {{importMode}} {{merge}} the last read {{<priority>}} should win.
> * Document it in [1]
> For both A and B the most or all occutences of {{<priority>}} should be removed from Portal Extension Quickstart.
> [1] [https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...]
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-2072) NoSuchDataException is thrown after importing pages through export/import tool.
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2072?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2072:
----------------------------------
Sprint: Sprint 83, Sprint 87 (was: Sprint 83)
> 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: 2 days, 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
10 years, 5 months