SmartGWT 2.4 migration Issues

[tgallage]

This is my current application environment :
1) Java 1.6, Smart GWT 2.2, GWT 2.0.3
2) All data sources are JSON RestDataSources.

We tried to upgrade above to SmartGwt 2.4 and GWT 2.2. I downloaded the SmartGwt 2.4 last release and updated the smartgwt.jar, msartgwt-skins.jar, gwt-servlet.jar libraries.

But We found a major issue in single DateItem fields in Dynamic/Search forms, started to appear as double Date range fields. This is really strange as we set them as DateItem fields.
We tried the nightly builds starting from of April 05, 2011. Now the above issue seemed to be fixed. But it is very strange as sort of new issue has arisen.

Now ComboBoxeItems in search forms are not sending the selected value to server side with latest smartgwt versions.
These are traces from Developer Console.


RPCRequest tab
===========

{
"actionURL":"tenderSupport!fetchCarrierTenderList.action",
"showPrompt":false,
"prompt":"Finding Records that match your criteria...",
"transport":"xmlHttpRequest",
"useSimpleHttp":true,
"promptStyle":"dialog",
"params":{
"_operationType":"fetch",
"_operationId":"",
"_startRow":0,
"_endRow":75,
"_sortBy":"-orderId"
},
"httpMethod":"GET",
"sendNoQueue":true,
"bypassCache":true,
"callback":{
"target":[RestDataSource ID:isc_CarrierTenderingDS_0]
},
"willHandleError":true,
"serverOutputAsString":true,
"clientContext":{
"requestIndex":3,
"$69t":null
},
"data":null
}


DSRequest Tab
==========

{
"dataSource":"isc_CarrierTenderingDS_0",
"operationType":"fetch",
"componentId":"isc_CarrierTenderingViewPanel_1_0",
"data":{
},
"startRow":0,
"endRow":75,
"sortBy":[
"-orderId"
],
"textMatchStyle":"exact",
"resultSet":[ResultSet ID:isc_ResultSet_0 (created by: isc_CarrierTenderingViewPanel_1_0)],
"callback":{
"caller":[ResultSet ID:isc_ResultSet_0 (created by: isc_CarrierTenderingViewPanel_1_0)],
"methodName":"fetchRemoteDataReply"
},
"willHandleError":true,
"showPrompt":false,
"prompt":"Finding Records that match your criteria...",
"clientContext":{
"requestIndex":3
},
"requestId":"isc_CarrierTenderingDS_0$6276"
}

[Isomorphic]

We show ComboBoxItems working fine. Please check if you have installed a getPickListFilterCriteria function that might be malfunctioning - check whether it's returning empty criteria and if so, if it appears to be due to what SmartGWT methods are returning, let us know what you think is wrong.

[tgallage]

This is the code which it has been working from version 1.3 to 2.2

DataSource carrierDataSource = CommonLookupDS.getLookupDS(LookupTypesClient.LOOKUP_CARRIERS_FOR_TENDERING);
final ComboBoxItem carrierCombo = new ComboBoxItem("carrierId", "Carrier");
carrierCombo.setOptionDataSource(carrierDataSource);
carrierCombo.setDisplayField("value");
carrierCombo.setValueField("key");
carrierCombo.setWidth(150);
carrierCombo.setWrapTitle(false);
carrierCombo.setAutoFetchData(false);

This ComboBoxItem is added to the SearchForm and user selects an item in the ComboBox. When fetch() is called on search form, we can't see value for "carrierId" going with the request.

[Isomorphic]

Jumping back a step, your upgrade procedure is woefully incomplete and you're quite possibly testing a flawed setup right now.

Correct installation procedures are here. Please do a correct install, retest, and if you're still seeing the issue, make sure that the actual files being delivered to the browser are from the new version (in the .js files such as ISC_Core.js, you can see a date stamp in the header if you look using Firebug's "Net" panel).

[tgallage]

We are using SmartGwt LGPL version with RestDataSource mechanism. I have been doing the steps you mentioned in setup always except the specific things relevant with SmartGWTEE.

I have attached our config files if you guys want to look at it.

[Isomorphic]

Your code doesn't reproduce a problem for us. Try a recent nightly - you mentioned an April 5th nightly, which may have had an overnight regression that's already fixed.

[tgallage]

Still no success. I tried all latest nightly builds.

[Isomorphic]

Ok, we're seeing what looks like the issue.
We'll be fixing this internally in the near future - in the meantime explicitly calling 'setCriteriaField()' on the item should resolve this issue for you

Thanks
Isomorphic Software

[tgallage]

great , that worked.
Also I tried the today May 02 Nightly build and the issue has been fixed in your side.

Thanks again.