[JBoss JIRA] Created: (GTNPORTAL-1663) The application registry is not able to properly import portlets with the same name
5:50 a.m.
The application registry is not able to properly import portlets with the same name
-----------------------------------------------------------------------------------
Key: GTNPORTAL-1663
URL: https://jira.jboss.org/browse/GTNPORTAL-1663
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Chris Laprun
If portlets from different wars or different PortletInvokers have the same name then
creating the content for the portlet will fail because the customization process only uses
the local portlet name instead of a fully qualified version.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:50 a.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-1663) The application registry is not able to properly import portlets with the same name
[
https://jira.jboss.org/browse/GTNPORTAL-1663?page=com.atlassian.jira.plug...
]
Chris Laprun updated GTNPORTAL-1663:
------------------------------------
Fix Version/s: 3.2.0-GA
Affects Version/s: 3.1.0-GA
The application registry is not able to properly import portlets with
the same name
-----------------------------------------------------------------------------------
Key: GTNPORTAL-1663
URL: https://jira.jboss.org/browse/GTNPORTAL-1663
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Fix For: 3.2.0-GA
If portlets from different wars or different PortletInvokers have the same name then
creating the content for the portlet will fail because the customization process only uses
the local portlet name instead of a fully qualified version.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 a.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-1663) The application registry is not able to properly import portlets with the same name
[
https://jira.jboss.org/browse/GTNPORTAL-1663?page=com.atlassian.jira.plug...
]
Chris Laprun updated GTNPORTAL-1663:
------------------------------------
Attachment: GTNPORTAL-1163.patch
Simple fix for the issue. Needs to be tested more properly, though.
The application registry is not able to properly import portlets with
the same name
-----------------------------------------------------------------------------------
Key: GTNPORTAL-1663
URL: https://jira.jboss.org/browse/GTNPORTAL-1663
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Fix For: 3.2.0-GA
Attachments: GTNPORTAL-1163.patch
If portlets from different wars or different PortletInvokers have the same name then
creating the content for the portlet will fail because the customization process only uses
the local portlet name instead of a fully qualified version.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:27 a.m.
New subject: [JBoss JIRA] Resolved: (GTNPORTAL-1663) The application registry is not able to properly import portlets with the same name
[
https://jira.jboss.org/browse/GTNPORTAL-1663?page=com.atlassian.jira.plug...
]
Chris Laprun resolved GTNPORTAL-1663.
-------------------------------------
Assignee: Chris Laprun
Resolution: Done
The application registry is not able to properly import portlets with
the same name
-----------------------------------------------------------------------------------
Key: GTNPORTAL-1663
URL: https://jira.jboss.org/browse/GTNPORTAL-1663
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Assignee: Chris Laprun
Fix For: 3.2.0-GA
Attachments: GTNPORTAL-1163.patch
If portlets from different wars or different PortletInvokers have the same name then
creating the content for the portlet will fail because the customization process only uses
the local portlet name instead of a fully qualified version.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 p.m.
New subject: [JBoss JIRA] Closed: (GTNPORTAL-1663) The application registry is not able to properly import portlets with the same name
[
https://issues.jboss.org/browse/GTNPORTAL-1663?page=com.atlassian.jira.pl...
]
Hang Nguyen closed GTNPORTAL-1663.
----------------------------------
The application registry is not able to properly import portlets with
the same name
-----------------------------------------------------------------------------------
Key: GTNPORTAL-1663
URL: https://issues.jboss.org/browse/GTNPORTAL-1663
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Assignee: Chris Laprun
Fix For: 3.2.0-GA
Attachments: GTNPORTAL-1163.patch
If portlets from different wars or different PortletInvokers have the same name then
creating the content for the portlet will fail because the customization process only uses
the local portlet name instead of a fully qualified version.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5116
days inactive
5166
days old
4 comments
2 participants
participants (2)
-
Chris Laprun (JIRA) -
Hang Nguyen (JIRA)