sgwt 3.0 FF7.0
Hi,
I moved from the 2.4 to 3.0 version and encountered with a behavior I never saw in my application before. Almost all the SelectItems show additional “undefined” value at the bottom. I set the values map with item.setValueMap(map), where the map is a LinkedHashMap instance. Sure I check the map before assigning it to the item and it has no “undefined” value.
Has anybody encountered with something like that?
Any help or suggestions would be very appreciated.
You mentioned FF, but this would happen of you were testing in Chrome Development mode. No one else has reported this for FF.
Unfortunately I just can confirm that it happens in FF7.0 (dev mode)
Be sure you’ve run a GWT compile and cleared the browser cache. If it still occurs, please put together a minimal, ready-to-runtest case demonstrating the issue.
I found out that the SelectItem (or PickListMenu) sends additional request to the server through the DataSource that is set to a ValuesManager by valuesManager.setDataSource(dataSource); and the DynamicForm “form” this SelectItem belongs to is set to this valuesManager by valuesManager.addMember(form). The request looks like that:
componentId isc_PickListMenu_0
_dataSource isc_PagedRestDataSource_3
_endRow 75
_operationType fetch
_startRow 0
_textMatchStyle startsWith
isc_dataFormat json
isc_metaDataPrefix _
It looks like the data retrieved by this request are combined with the valueMap I set for that selectItem.
As soon as I added the selectItem.setAutoFetchData(false); this additional request vanished and all the unwanted options as well.
Could you confirm that what I did is what is correct that should be done in this case?
In what case? Did you mean to attach a test case?