Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Incomplete
Priority: Trivial Trivial
Assignee: rogerk
Reporter: kv.jensen
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

SelectMany tags do not update correctly using ajax in IE

Created: 15/Jan/13 02:46 PM   Updated: 09/Sep/13 01:54 PM   Resolved: 09/Sep/13 01:54 PM
Component/s: ajax
Affects Version/s: 2.1.6
Fix Version/s: None

Time Tracking:
Not Specified


Glassfish open source edition ver.
Microsoft Internet explorer: 9.0.8112

Issue Links:

Participants: kv.jensen, Manfred Riem and rogerk

 Description  « Hide

When performing an partial update to populate a SelectManyXXX tag and then want to submit a new partial update (ajax) of the SelectManyXXX tag when click (i.e. clicking the checkbox) no values are submitted.

If a full post form submit is issued the values are indeed submitted.

Note that the GUI updates correctly and the dynamic checkboxes are shown and can be selected. Selecting them fires the ajax request correctly BUT NO VALUES ARE SUBMITTED updating the backend to an empty list.
This only happens in Internet Explorer.

Updated by :
<h:inputText value="#{CommodityLine.pallabel}">
<f:ajax event="change" render="serialBox"></f:ajax>

The selectmanytag:
<h:selectManyCheckbox id="palletSerials" layout="pageDirection"
<f:selectItems value="#{OnlineBeanHandler.allPalletSerials}"></f:selectItems>

The listening setter recieves an empty array/list/aggregate when making the partial update.

Manfred Riem added a comment - 09/Sep/13 01:54 PM

Closing because of inactivity

Manfred Riem added a comment - 12/Aug/13 04:48 PM

Lowering priority because of inactivity

rogerk added a comment - 10/Jul/13 02:33 PM

Lowering priority because of no response.

rogerk added a comment - 06/May/13 05:40 PM

Can you tell me the relationshio with the inputText and the SelectMany components in your example? Can you provide a small webapp that demonstrates the issue? You can send it to


Manfred Riem added a comment - 18/Feb/13 02:28 PM

Can you verify if this is still a problem against the latest 2.1 release?