[JBoss JIRA] Created: (GTNPORTAL-2054) Navigation is not being imported on fresh installation for multiple extensions targeting the same site's navigation.
10:53 a.m.
Navigation is not being imported on fresh installation for multiple extensions targeting
the same site's navigation.
--------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:04 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-2054) Navigation is not being imported on fresh installation for multiple extensions targeting the same site's navigation.
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Thomas Heute commented on GTNPORTAL-2054:
-----------------------------------------
I don't understand
Navigation is not being imported on fresh installation for multiple
extensions targeting the same site's navigation.
--------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:27 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-2054) Navigation is not being imported on fresh installation for multiple extensions targeting the same site's navigation.
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet commented on GTNPORTAL-2054:
----------------------------------------
the default mode now is "conserve" that is a safe mode where nothing is modified
on subsequent boots.
have you tried other import mode such as merge or insert to see if it works ? those import
modes are designed for the wsrp use case.
Navigation is not being imported on fresh installation for multiple
extensions targeting the same site's navigation.
--------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-2054) Navigation is not being imported on fresh installation for multiple extensions targeting the same site's navigation.
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Nick Scavelli commented on GTNPORTAL-2054:
------------------------------------------
Changing default mode to merge best mimics previous behavior, however you run the risk
default config overwriting customizations. What would be nice is to explicitly set the
import mode to "conserve" for the default portal, then for configuration which
doesn't specify an import mode, default to merge. However there is an ordering
dependency where the default portal needs to be "imported" first, and I'm
not familiar enough with the code to assume this.
Navigation is not being imported on fresh installation for multiple
extensions targeting the same site's navigation.
--------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-2054) Navigation is not being imported on fresh installation for multiple extensions targeting the same site's navigation.
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet commented on GTNPORTAL-2054:
----------------------------------------
We can set a default behavior when no one is specified on the UserPortalConfigService
itself that would be set to merge for instance.
As for the default portal itself, as it is not an *external* component plugin, it will
always be applied first before the external component plugins, as far as I know, WSRP is
an external component plugin.
Navigation is not being imported on fresh installation for multiple
extensions targeting the same site's navigation.
--------------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:32 a.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-2054) Navigation default import mode be configurable for external component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet updated GTNPORTAL-2054:
-----------------------------------
Summary: Navigation default import mode be configurable for external component
plugins and set by default to merge (was: Navigation is not being imported on fresh
installation for multiple extensions targeting the same site's navigation.)
Assignee: Julien Viet
Navigation default import mode be configurable for external component
plugins and set by default to merge
---------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:32 a.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-2054) Navigation default import mode should be configurable for component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet updated GTNPORTAL-2054:
-----------------------------------
Summary: Navigation default import mode should be configurable for component plugins
and set by default to merge (was: Navigation default import mode be configurable for
external component plugins and set by default to merge)
Navigation default import mode should be configurable for component
plugins and set by default to merge
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:42 a.m.
New subject: [JBoss JIRA] Resolved: (GTNPORTAL-2054) Navigation default import mode should be configurable for component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet resolved GTNPORTAL-2054.
------------------------------------
Fix Version/s: 3.2.0-M02
Resolution: Done
Navigation default import mode should be configurable for component
plugins and set by default to merge
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
Fix For: 3.2.0-M02
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 a.m.
New subject: [JBoss JIRA] Reopened: (GTNPORTAL-2054) Navigation default import mode should be configurable for component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Chris Laprun reopened GTNPORTAL-2054:
-------------------------------------
With the current fix, I still need to explicitly set importMode to merge in the WSRP
config for the admin page to appear.
Navigation default import mode should be configurable for component
plugins and set by default to merge
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
Fix For: 3.2.0-M02
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-2054) Navigation default import mode should be configurable for component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Julien Viet commented on GTNPORTAL-2054:
----------------------------------------
it's not what the unit test say.
can you investigate and add a break point in createPageNavigation on the line
ImportMode importMode;
and determine which mode is actually used ?
thanks
Navigation default import mode should be configurable for component
plugins and set by default to merge
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
Fix For: 3.2.0-M02
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] Resolved: (GTNPORTAL-2054) Navigation default import mode should be configurable for component plugins and set by default to merge
[
https://issues.jboss.org/browse/GTNPORTAL-2054?page=com.atlassian.jira.pl...
]
Chris Laprun resolved GTNPORTAL-2054.
-------------------------------------
Resolution: Done
Apparently, I might not have properly updated my local version when I tried the test last
night, since I have tried again with a properly updated version and I can now confirm that
the issue is resolved. Thanks!
Navigation default import mode should be configurable for component
plugins and set by default to merge
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2054
URL: https://issues.jboss.org/browse/GTNPORTAL-2054
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
Assignee: Julien Viet
Fix For: 3.2.0-M02
NavigationImporter is called multiple times inside NewPortalConfigListener with import
mode conserve. So during a fresh installation, the NavigationImporter imports the data for
a site, but when it's called again (another extension), the navigation exists and
conserve does nothing because the navigation for that site already exists. This is not
backwards compatible with previous versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5164
days inactive
5170
days old
10 comments
4 participants
participants (4)
-
Chris Laprun (JIRA) -
Julien Viet (JIRA)
-
Nick Scavelli (JIRA)
-
Thomas Heute (JIRA)