Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Criteria returning [object Object]

    SmartGWT is LGPL 3.0p
    SmartClient Version: SC_SNAPSHOT-2012-01-12_v8.2p/LGPL Development Only (built 2012-01-12)

    Browser 1 is IE7
    Browser 3 is IE9 set to IE7 mode

    I'm revising an application from older releases of GWT and SmartGWT. The application had multiple performance issues which were not related to either GWT or SmartGWT. Some of the screens in the application use SelectItems that allow multiple selections. Apparently the way the multiple selections get stored in the Criteria object has changed over time. The application was expecting a String value containing a comma-separated list when using criteria.getAttribute(). The expected value is multiple numeric IDs. The new SmartGWT returns a bracketed list of values separated by spaces and commas as in: [31, 4475]
    I modified that code that processes these values so an array of valid numbers is the result. This criteria gets processed by two queries. The first query runs a count(*) using the criteria to determine how large the result set will be. The second query retrieves the data with some paging information including starting and end rows and how many rows per page to return. The criteria is modified for the second query (adding the paging information). When the client-side code attempts to get the multiple ids the second time - the getAttribute method returns [object Object] and the selected IDs are not present in the result. The interesting part of this is that this only happens with Browser 1 (IE7). Unfortunately that is the only browser supported by the company that owns this software.

    Any suggestions on why the [object Object] is returned (and how to get the actual numeric IDs)?

    If run a getValues() on the criteria and iterated the contents to the SC log I see no difference in the displayed values between the criteria that returns [31, 4475], and the criteria that returns [object Object].

    Some other points:

    OS that works is Windows 7 - OS that fails is a virtual server running Windows Server 2008.

    Firefox runs without errors on the same server as the failed IE7.
Working...
X