Bug 1094772
| Summary: | Different Portlet preference for remote portlets added on the same page | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | Anurag <adebnath> |
| Component: | Portal | Assignee: | Nobody <nobody> |
| Status: | CLOSED UPSTREAM | QA Contact: | vramik |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | epp-bugs, nobody, ppalaga |
| Target Milestone: | ER04 | ||
| Target Release: | 6.2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the way portlet preferences were stored in WSRP could result in two instances of the same WSRP portlet to share the same portlet ID. This resulted in one portlet overwriting the preferences of the other portlet. The fix implements improvements to WSRP portlet preference storage by storing preferences based on a unique ID generated for each portlet instance. This separates portlet preferences from other portlet instances.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:35:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Merged. Juraci Paixão Kröhling <jpkroehling> updated the status of jira GTNWSRP-376 to Closed Honzo, as stated above in comments and in Target Milestone field, this fix arrives in ER4, therefore you set the status to ON_QA too early. Setting back to MODIFIED. Verified in ER04. Both the portlets have their individual preferences (colors). This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Description of problem: When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well. Ideally, portlets should get their own preference/s. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: - Deploy PortletPreferencesPortlet.war . The portlet is already marked remotable. Use the Application Registry to register the portlet. - Next, I refreshed the selfv2 WSRP consumer, which should make the PortletPreferencesPortlet available in the portlet --> remote view of the Application Registry. - Create a new page (eg: http://localhost:8080/portal/classic/home/testRemote), add the remote portlet twice. -Using edit mode on the two portlet instances (via the interface itself), change the 'color' preference . Actual results: When the colour preference of one portlet is changed, the second one added to the page also takes the same preference. Expected results: Both the portlets should have their individual preference/s. Additional info: