-
1. Re: New bug in RF 4.5.3 collapsiblePanel
michpetrov Mar 16, 2015 8:27 AM (in response to edilmar)The collapsible panel is not processed when it's collapsed, since you have switchType="client" the server will always treat it as collapsed and skip it. You need to use switchType="ajax".
-
2. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Mar 16, 2015 11:27 AM (in response to michpetrov)Hi,
Strange that I use this component since RF 4.0 to 4.5.2 with switchType="client" and I think it wouldn't block internal AJAX components to work, like a4j:commandButton and rich:autoComplete. I tested also rich:autoComplete and it also doesn't work in RF 4.5.3.
And, also using switchType="ajax/server" and expanded="false", it continues with same problem. But if I change to switchType="ajax" and expanded="true" it works. My problem is that I really need expanded="false", to just show the internal components if the user needs this, because the interface requires this.
And one more test: switchType="client" and expanded="true" it works too.
Then, I think this is a real bug in collapsiblePanel with expanded="false".
-
3. Re: New bug in RF 4.5.3 collapsiblePanel
michpetrov Mar 17, 2015 6:51 AM (in response to edilmar)switchtype="ajax" should work, I tested it with that, and it would load the content when the panel expands so you wouldn't need to click the button, but I do not know your use-case. I wanted to recommend collapsing the panel with document.ready but that doesn't seem to work well, I'll take a look at it. It's become necessary for the collapsible panel to be aware of its state when its children are processed so if you explicitly declare that panel is collapsed the server will treat it that way.
-
4. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Mar 17, 2015 9:37 AM (in response to michpetrov)Hi,
It is simple for you to simulate my use case. Just create a collapsiblePanel with expanded="false" and you will see that client/ajax/server (none of them) work in RF 4.5.3, but the component works fine with versions older.
-
5. Re: New bug in RF 4.5.3 collapsiblePanel
michpetrov Mar 17, 2015 11:36 AM (in response to edilmar)I took your example and changed the switchtype, it is working for me. What version of JSF and what server are you using? If you can create a reproducer I can take a look at it.
-
6. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Mar 17, 2015 3:40 PM (in response to michpetrov)I use Glassfish 3.1.2.2 + javax.faces.jar 2.1.29 + CDI/Weld + DeltaSpike GroupedConversationScoped + Hibernate 4.2.7.
If you can, please access this link with my test: http://sitesat.intersite.com.br:81/sitesat2-cte/teste.jsf
-
7. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Mar 18, 2015 11:02 AM (in response to edilmar)I think it is possible that some solution of bugs [RF-13988] collapsiblePanel stops rendering of following components - JBoss Issue Tracker, [RF-13958] collapsibleSubTable: the most nested CST remains collapsed after parent CST re-expands - JBoss Issue Tracker or the comment "We have also fixed server-side issues with visiting components that were not supposed to be visited (such as unrendered columns or collapsed collapsiblePanels)." is the cause of the new problem.
-
8. Re: New bug in RF 4.5.3 collapsiblePanel
arean.tromp Mar 24, 2015 10:09 AM (in response to edilmar)Hi,
Just wanted to confirm this issue with RF 4.5.3
In my case there are multi collapsiblePanels with switchType="client" and expanded="false".
In each panel there are multiple check boxes. All check boxes are submitted with a one a4j:commandButton.
Changed checkboxes are not posted to the backing bean, can confirm it worked fine with RF 4.3.7.
-
9. Re: New bug in RF 4.5.3 collapsiblePanel
michpetrov Mar 24, 2015 10:49 AM (in response to edilmar)I see that it doesn't work but I need to see the code. Though from what I see you still got switchType="client" on the first panel.
The current state isn't ideal however, can you file a new issue?
-
10. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Mar 24, 2015 4:33 PM (in response to michpetrov)Just remembering that the real problem is just => expanded="false".
I think it is possible that some solution of bugs [RF-13988] collapsiblePanel stops rendering of following components - JBoss Issue Tracker, [RF-13958] collapsibleSubTable: the most nested CST remains collapsed after parent CST re-expands - JBoss Issue Tracker or the comment "We have also fixed server-side issues with visiting components that were not supposed to be visited (such as unrendered columns or collapsed collapsiblePanels)." is the cause of the new problem.
-
11. Re: New bug in RF 4.5.3 collapsiblePanel
ijpnw Apr 1, 2015 7:33 PM (in response to edilmar)I'm also having issues with expanded="false" collapsible panels in RF 4.5.3. Not the same issue, but probably related. In my case I'm getting 'duplicate ID found in view exception' and can see in the log that RF is trying to render the first element on the collapsible panel twice:
+id: proteinDetailsExternalIdPanel
type: org.richfaces.component.UICollapsiblePanel@4c94de95
+id: j_id101
type: javax.faces.component.UIPanel@41a12f7a
+id: j_idt335 <===============
type: javax.faces.component.html.HtmlOutputText@3d34143f
+id: j_idt335 <===============
type: javax.faces.component.html.HtmlOutputText@261d537d
This is happening immediately when the page is rendered, not when I try to expand the panel. The problem is not happening with earlier version of RF and initially expanded panels. Unfortunately I haven't been able to reproduce the problem with simple test application, but it definitely looks to me that a bug fix implemented in RF 4.5.3 causes this.
-
12. Re: New bug in RF 4.5.3 collapsiblePanel
bleathem Apr 2, 2015 12:39 PM (in response to edilmar)Would you please file a new jira tracking this potential regression? Please also add a comment to RF-13988 linking to the new issue.
-
13. Re: New bug in RF 4.5.3 collapsiblePanel
ijpnw Apr 2, 2015 1:51 PM (in response to bleathem)Created new issue: https://issues.jboss.org/browse/RF-14010
-
14. Re: New bug in RF 4.5.3 collapsiblePanel
edilmar Apr 15, 2015 2:14 PM (in response to ijpnw)Is there some plan to solve the problem with expanded="false" in RF 4.5.5?
Because I already tested with RF 4.5.4 and the problem continues the same.