> What kind of scope does your bean have?
Currently I am using the session scope, but I would like to use request scope
in combination with <t:saveState> to save the dialgue state in the future. I
use preserveDataModel=false everywhere on the tomahawk tables.
Nevertheless: I think that's not the problem. The behaviour I describe can be
reproduced with demo application, if I add a Test Bean like
private class TestBean implements Serializable{
private String _s1;
private String _s2;
// + getter and setter
}
and add a list of TestBeans to the TabbedPaneBean of the Tomahawk example like
List<TestBean>
and insert a data table to the demo like:
<t:panelTab id="tab1" label="#{example_messages['tabbed_tab1']}"
rendered="#{tabbedPaneBean.tab1Visible}">
<t:dataTable
headerClass="myTableHeader"
rowClasses="myTableRow1,myTableRow2"
var="r"
preserveDataModel="false"
preserveRowStates="false"
preserveSort="false"
value="#{tabbedPaneBean.testBeans}">
<h:column>
<f:facet name="header">
<h:outputText
value="--Header 1 --" />
</f:facet>
<t:inputText
id="inputField002"
value="#{r.s1}" />
</h:column>
<h:column>
<f:facet name="header">
<h:outputText
value="--Header 2 --" />
</f:facet>
<t:inputText
id="inputField001"
value="#{r.s2}" />
</h:column>
</t:dataTable>
then input made in the input table will not be written into the backing beans,
unless you hit the demo's "Common submit button" before you switch the tabs.
Or in other words, if you switch the tabs directly, the entered information
will be lost.
I am going to check whether a bug for this issue is already open. I am will ing
to open a bug report, unless you oppose.
Regards,
Christian
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED]
