help getting current tab on client side tab panel

[jersinghaus]

I've got a tab panel set up for client side switching (switchType="client").

The submit trigger for the page is a double click on a data grid within the tab panel. This is an rcfaces dataGrid.

I'd like to get the active tab name in my bean so I can execute the double click properly.

My tab panel is set up this way:

<rich:tabPanel valueChangeListener="#{taskBean.valueChanged}" style="height: 395px;" switchType="client" width="430" headerAlignment="left"
 binding="#{taskBean.tabPanel}" value="#{taskBean.currentTab}">

Inside my bean, the method called from the double click submit action has this:

UITabPanel tabPanel = (UITabPanel) getTabPanel();
 Object tabValue = tabPanel.getValue();

No matter what tab is clicked, tabValue holds the same (default value - 1st tab) value.

Should tabValue hold the current tab even for a tab with switchType="client"?

If I use value change listeners in this scenario, the listeners aren't called until after the dataGrid action method is called.

Maybe I need to make an ajax call to pass the current tab to the bean?

If this is the case, is there an example on how to do this?


Thanks,
Joe

[sergeysmirnov]

do you have a h:form inside the tab or outside the tabPanel?

[jersinghaus]

Outside. I have just one h:form for the whole page.

[nbelaevski]

Hello!

Can you please provide sample code to reproduce the problem? Thank you in advance!

[jersinghaus]

I've placed a sample project war file here:
http://www.nmda.nmsu.edu/download/temp.html

Also there is a link to the java source used in the war (it's actually a text file - I couldn't get my IIS server (I hate IIS) to download a file with a .java extension).

Let me know if you need anything else.


Thanks,
Joe

[jersinghaus]

I forgot to note that in this sample project, I could not get the valueChangeListener to fire for some reason.

[nbelaevski]

Joe,

thank you for reporting the problem! I've filed it into JIRA as http://jira.jboss.com/jira/browse/RF-78. The issue will be fixed immediately.

[jersinghaus]

Hi Nick,

Does RF-78 refer to the problem I was having with the "binding" attribute or the "value" attribute?

The "value" attribute is fixed - thanks for that work!

But I still see that the "binding" attribute does not return the currently selected tab.

Evaluating the "binding" method getValue() returns the equivalent of getOldValue() on a "valueChangeListener." So it's a tab click behind. (But I can't use the "valueChangeListener" because it executes after the methods that initiate the form submit and do logic.)

Evaluating the "binding" method getSelectedTab() returns null.

I use the "value" attribute to have the last selected tab "reselected" when navigating back to the page with the tabs.

I'm trying to use the "binding" attribute to process data on submission.


Thanks,
Joe

[nbelaevski]

Joe,

sounds like the component hadn't succeded to complete the whole lifecycle by the moment you try to get the new value. It happens at UPDATE_MODEL_VALUES phase if component is not immediate and at APPLY_REQUEST_VALUES phase if component is immediate. Can you please check if that is the case?