Bug 1032715
| Summary: | Provide functionality to reset the portlet view | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | Martin Weiler <mweiler> |
| Component: | Portal | Assignee: | Nobody <nobody> |
| Status: | NEW --- | QA Contact: | Marek Baluch <mbaluch> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1.0 | CC: | bdawidow, epp-bugs, laszlo.van.den.hoek, nobody, theute, tkyjovsk |
| Target Milestone: | ER01 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | 6_3 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previous versions of PortletBridge could not reset the state of a JSF portlet to it's default state. In cases where the navigation was contained inside a JSF portlet, the navigation could not be reset until the session expired. The fix includes PortletBridge 3.3.1 in this release of JBoss Portal, which correctly returns a JSF portlet to it's default state when required. This behavior is documented in the PortletBridge project at https://docs.jboss.org/author/display/PBR/Save+Bridge+Request+Scope+after+Render+complete
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Enhancement | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Martin Weiler
2013-11-20 16:13:59 UTC
Hi Martin, Please, can you add more details to the request ? Do you mean ... ? a) Portlets based in PortletBridge JSF, to reset the JSF state to return to default view. b) Pages with multiples portlets, each one with one state (i.e. EDIT mode and maximized), and reset portal page state. c) Both cases ? Thanks, Lucas Ken has pointed that JBoss Portal 6.1.1 will include PortletBridge 3.1.1 with a feature to not retain state (in other words to set the view for JSF portlets): https://docs.jboss.org/author/display/PBR/Save+Bridge+Request+Scope+after+Render+complete (In reply to Lucas Ponce from comment #3) > PortletBridge 3.1.1 Surely you mean PortletBridge 3.3.1? The version included with JPP 6.1.0 is 3.2.1. PortletBridge 3.3.1 Sorry, I had a typo in my previous comment. Lucas, the request was for scenario a), which is covered with the new PBR bridge feature. Feel free to close this bz. Yes, I can verify that this feature of PBR is really working. Based on the report from Anurag, I have to confirm that it seems PBR retains the state of JSF portlets again no matter what configuration you have. Steps to reproduce (you can use reproducer provided by Anurag) 1. Deploy portlet 2. Add it to some page and go to there 3. Fill something into the input and submit, now you are on the step 2 4. Go to some other page 5. Go back to the page with reproducer, portlet should have reset the view into its initial state but you can still see the step 2 hanging there So I managed to test it with older versions and result is still the same. I made a reproducer from one of the example portlets in PBR, so you can check it for yourself in earlier version of JPP https://github.com/pmensik/portletbridge/tree/BZ-1032715_reproducer I also have added integration test into the PBR testsuite and strange thing is that it passes (I mean you leave the portlet in step two, go to some url, go back and portlet shows you the homepage), you can check it in the other branch of my fork https://github.com/pmensik/portletbridge/tree/BZ-1032715 Just do mvn verify -P browser-phantomjs,integration-tests,jbossas-managed-7 -Dtest=RequestScopeRetainingTest The resolution in comment #3 refers to PBR-499, which is related to state being retained between requests when it shouldn't. This BZ relates to resetting the view id of a portlet, and is unrelated to whether state is being retained between Render requests or not. |