[richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work

[Mike Kienenberger (JIRA)]

    [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707392#comment-12707392 ] 

Mike Kienenberger commented on RF-11417:
----------------------------------------

It's been 10 months, and 4.2.2 final is now out.   The posted workaround using switchType=ajax and onenter in the discussion thread doesn't work.

Maybe it's time for you to remove the attributes, or at least document that they don't work.

After several hours, I was able to sort of able make this work, with a ugly slow double-page-redraw, using the following pattern:

1) Change switchType from ajax to server
2) Define an a4j:function that executes the original rich:tab action.
3) Make the rich:tab's onheaderclick call the previously-defined function.
4) make sure the action called also updates the rich: selectedTab backing bean value.

While this is tolerable for my development environment, it won't be suitable for a production app.

Various other attempts to make this work would call the server-side java code, but not render the panel afterward (some permutations would render the tab before the action was called); or render the panel, but not call the code.
                
> Tab: investigate why @action does not work
> ------------------------------------------
>
>                 Key: RF-11417
>                 URL: https://issues.jboss.org/browse/RF-11417
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes
>    Affects Versions: 4.1.0.CR1
>            Reporter: Lukáš Fryč
>             Fix For: 4.3-Tracking
>
>
> Determine why rich:tab @action has not been implemented.
> Verify that its implementation can't affect current applications (and try to find possible workaround).
> Implement @action and @actionListener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira