In a VWG migrated app, we have a page where the user selects from 4 items in a combobox. Depending on previously-entered options on an earlier page, some of those items need to be removed to be made unavailable.
cboSizeType.SelectedIndex = 0
002652 Wisej: index out of bounds: 2 (0..0)
It seems WiseJ is not recognizing that there is an item at that position. See attached test-case.
Wisej optimizes the round trips. When you add an item and delete it before it’s sent to the client, the item is not sent at all (the list in your sample seems correct), but for the combobox it ended up sending back the request to remove the item as well, which doesn’t exist on the client.
Please login first to submit.