Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Selecting "delete portlet data before importing" when importing WSRP portlet data causes all existing WSRP portlets to be undeployed

Description

Selecting "delete portlet data before importing" when importing WSRP portlet data causes all existing WSRP portlets to be undeployed. This sounds exactly like the bug that was fixed by LPSA-9347: WSRP Portlets are not available after Importing LARClosed, but the error still persists in the following way.

Steps to Reproduce:

1. Deploy the WSRP portlet.
2. Navigate to "WSRP" section of Control Panel.
3. Navigate to the "Producers" tab.
4. Add a WSRP Producer and move the Hello World Portlet is in the "Current" column.
5. Copy URL for the created WSRP Producer.
6. Navigate to the "Consumers" tab.
7. Add a WSRP Consumer using the URL copied in step 5.
8. Go to Actions > Manage Portlets for the created WSRP Consumer.
9. Add the Hello World portlet as a new portlet on the WSRP Consumer. Name it Remote Hello World.
10. Go back to /web/guest/home.
11. Add the Remote Hello World portlet to the page.
12. Go back to "WSRP" section of Control Panel.
13. Using the Wrench icon in the top right, select "Export/Import".
14. Make sure everything under "Data" is selected and export the LAR.
15. Navigate to the Import tab.
16. Ensure that "Delete portlet data before importing" is checked and import the LAR that was exported in step 14.
17. Go back to /web/guest/home.

Expected Behavior:

The Remote Hello World portlet continues to show up.

Actual Behavior:

The Remote Hello World portlet shows up with a "This portlet has been undeployed. Please redeploy it or remove it from the page." message.

Activity

Show:

Pani Gui January 31, 2012 at 9:14 PM

PASSED Manual Testing following steps in description.

Reproduced on:
Tomcat 6.0 + MySQL 5. 6.0.12 EE.
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 636fedc2054be5f21fda9bd4491d497206b593c2. Plugins GIT ID: b8632915c91b631c277f8cd431ac0227c556be6d.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 951ba0761ba8f4af5743a73b3d4e7b328bc4d35c. Plugins GIT ID: 288b41595492c1b6a0eaa0f86a104323af96e853.

The existing WSRP portlet switches to be undeployed after importing WSRP portlet data.

Fixed on:
Tomcat 6.0 + MySQL 5. 6.0.x GIT ID: 617c094826cadf4e739e847fb399b04849d8d963. Plugins GIT ID: b2b7d4faaf9f21ef54ef5bc33a3feaaccfd9cd35.
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 636fedc2054be5f21fda9bd4491d497206b593c2. Plugins GIT ID: 28db533173f7172c23f8b0035bb177434d47979b.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 951ba0761ba8f4af5743a73b3d4e7b328bc4d35c. Plugins GIT ID: 6e1536c4410c39f2f540616553ff0bda7bff45f6.

The existing WSRP portlet continues to show up.

Michael Saechang January 25, 2012 at 11:02 AM

Committed on:
6.0.x Plugins GIT ID: e79c872702836642a529e6638d757270bd91bd27.
6.2.x Plugins GIT ID: df972471758f406aab0c1738f2a9f83c5ca5241a.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x
6.0.x

Backported to Branch

Committed

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created January 18, 2012 at 5:12 PM
Updated June 24, 2023 at 3:43 PM
Resolved March 12, 2012 at 3:05 PM