Description of problem: There is no change when import portlet to window. You have to sign out and sing in again to view changes applied. How reproducible: both producer and consumer started (I use different set of ports) and producer have some portlet deployed Steps to Reproduce: 1. open consumer and sign in as a root 2. go to wsrp page and register producer 3. export some portlet and import it into some window 4. check if the window contains imported portlet Actual results: Old portlet present. Expected results: Imported portlet present. Additional info: When you log out and in imported portlet is present.
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