Bug 873733
Summary: | WSRP - portlet import doesn't work | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | vramik |
Component: | Portal | Assignee: | claprun <claprun> |
Status: | CLOSED WONTFIX | QA Contact: | vramik |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.x | CC: | bdawidow, epp-bugs, hfnukal, mvanco, theute |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 6.0.x | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Due to an issue with portal data caching on the consumer side, the portlet present before a WSRP import might still be visible after the import, when it should have changed. To work around the issue, users may need to log out and log back into the portal to see changes made after a WSRP portlet import.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-20 11:39:06 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: |
Description
vramik
2012-11-06 15:31:53 UTC
The issue is still present in jpp6.0.er04.2 where is wsrp 2.2.1.CR01-redhat-1 I tried verify on gatein-master and there is still issue too. Chris Laprun <chris.laprun> updated the status of jira GTNWSRP-328 to Reopened Chris Laprun <chris.laprun> made a comment on jira GTNWSRP-328 Verified that if consumer and producer are running on separate process, then the issue occurs. The issue doesn't happen if both consumer and producer are running in the same AS instance. Chris Laprun <chris.laprun> made a comment on jira GTNWSRP-328 Thinking more about it, I believe it's acceptable to require users to log out and back in to see changes, though obviously not optimal. Not sure why it's only required when producer and consumer run in different AS instances. Because this is minor and there is valid workaround I'm setting it as WON'T FIX. Hi Bolek/Chris, unfortunately this is a regression since EPP 5.2, there was/is a set of tests for wsrp import and it always expected immediate import (and it always worked). I don't agree with setting as won't fix (even that's a minor). If you insist on not fixing the issue, then we have to update the tests to change import verification and it should be also included in documentation (wrsp, part about import & export). Thanks for the update. Wasn't aware it is a regression. Still it looks minor and has valid workaround. On the dev side we simply won't have necessary bandwidth to fix it within current time constraints for JPP 6. Please update the tests |