From: Ken Paulsen <Ken.Paulsen_at_Sun.COM>
Date: Mon, 16 Mar 2009 10:07:43 -0700

Hi Stephan,

I am just making a guess here, but perhaps the disabled property is interfering?  Was the field originally disabled when the content was rendered and then changed to "enabled" via JS?  If the server-side thinks the component was diabled when the data is submitted, it won't look for a value from the browser.

Good luck!

Ken

Huber, Stephan wrote:

Hi,

 

I've discovered some strange behavior regarding the filter panel in the woodstock table component (<webuijsf:table/>). The filter panel contains several components like dropdowns, checkboxes and a text field (<webuijsf:textfield/>). The strange thing now is that when I enter a value in the text field and click ok to submit the filter panel, the value is not submitted correctly - the property for the text field is still null. But when I open the filter for the second time and enter a value in the text field, the corresponding property is filled correctly with the given value.

 

<code>

<td><div style="width: 5px;"/></td>

<td>

<webuijsf:textField id="lotNoTextField" columns="25" text="#{YieldAnalysisBean.lotNoTextField}"

disabled="#{!YieldAnalysisBean.periodLotNoSelectedOption}"/>

</td>

</code>

 

The corresponding setter is not called for the first time - any ideas?

 

<code>

/**

* @param lotNoTextField

* the lotNoTextField to set

*/

public final void setLotNoTextField(final String lotNoTextField) {

this.lotNoTextField = lotNoTextField;

}

</code>

 

The other components in the filter panel do work well (even on first submit).

 

Any help would be greatly appreciated.

 

Best regards

 

- Stephan