Setting a FieldValueExtractor on a DataSourceField generates IllegalArgumentException about smartgwt

[GoogleCodeExporter]

yeah, that api has not yet been implemented.

Original comment by [email protected] on 14 Dec 2008 at 3:37

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in SVN.

Sample usage :

DataSourceTextField customField = new DataSourceTextField("countryCode", "Code 
/ Continent");
customField.setFieldValueExtractor(new FieldValueExtractor() {
    public Object execute(Object record, Object value, DataSourceField field, String fieldName) {
        String countryCode = XMLTools.selectString(record, "countryCode");
        String continent = XMLTools.selectString(record, "continent");
        return countryCode + "/" + continent;
    }
});

Original comment by [email protected] on 17 May 2009 at 3:01

• Changed state: Fixed
• Added labels: SmartGWT-1.0b3, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I am having exactly the same problem here. Updated to GWT 1.1 already, but 
nothing
changed at all. There is also no note about FieldValueExtractor interface in the
release notes.

Original comment by [email protected] on 29 May 2009 at 11:05

[GoogleCodeExporter]

Please post a standalone test case. The code snippet I posted works fine when 
used with the Showcase samples 
Country Datasource.

Original comment by [email protected] on 29 May 2009 at 11:12

[GoogleCodeExporter]

Unfortunately I can not post a standalone test case, because my company policy 
does
not allow posting any of their code. But I can assure you, that my code looks 
very
similar to your example.

The only distinction is, that I am using a server response in XML format rather 
than
parsing a static XML-File.

My stacktrace looks exactly the same.

I am just wondering, because the API change history does not say anything about 
the
FindValueExtractor either.

Original comment by [email protected] on 29 May 2009 at 12:26

[GoogleCodeExporter]

The standalone test case doesn't have to be your company code. Just create a 
new simplified sample, or 
modify a showcase sample so that the error is reproduced.

Also make sure your xml response has the correct content-type header.

The API hasn't changed. Previously the implementation didn't quite exist (as 
noted in by the reporter of this 
issue) but it now does. 

Again, I have tested that it works using this API with the Country XML 
DataSource. Unless you create a sample 
that reproduces the issue, we cannot tell whats going on. 

Original comment by [email protected] on 29 May 2009 at 12:50