GI 3.2 to 3.7 Development

That's the same pattern I'm using to filter a large dataset, but I use a small jsx3.gui.Dialog that implements a paged Matrix. A similar transformation is triggered for a view filter and is set on the incremental change event for a TextBox.

The XSL:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output encoding="UTF-8" indent="yes" omit-xml-declaration="yes"/>
<xsl:param name="searchFilter"></xsl:param>
<xsl:template match="/">
<xsl:variable name="lowerCase">abcdefghijklmnopqrstuvwxyz</xsl:variable>
<xsl:variable name="upperCase">ABCDEFGHIJKLMNOPQRSTUVWXYZ</xsl:variable>
<xsl:element name="data">
<xsl:attribute name="jsxid">jsxroot</xsl:attribute>
<xsl:copy-of select="//record[starts-with(translate(@jsxtext,$lowerCase,$upperCase),translat e($searchFilter,$lowerCase,$upperCase))]"/>
</xsl:element>
</xsl:template>
</xsl:stylesheet>

I also keep the original CDF and switch it to a filtered CDF in case the user removes the filter request.

--Vic

One reason that the pure JSP may not have had an issue with the large list was that the page formatting was done on the server side and had the full resources afforded to it by the web server. When you use GI, or any Ajax technique, to retrieve information and then format it, you are using the browser's resources to do most of the work.

When I build my JavaScript functions to create the request and process the response for such a large list, I make sure that I'm using the asynchronous approach as much as possible. For example, to retrieve a list of currency codes, I use jsx3.sleep to break up the call stack:

jsx3.sleep(function(){app.customer.services.callGetListOfValues(CURRENCY_CODE);} );

and then in that function, it will subscribe to the response for data handling in a callback:

objService.subscribe(jsx3.net.Service.ON_SUCCESS, app.customer.services.onGetListOfValuesSuccess);

When I post process the response for use in a Matrix component, I set the "XML Bind" property to "Bound" so that when I set the document in the Local Data Cache the Matrix is updated without a specific repaint.

If you try to fetch and process data in a single function, it may be part of the frozen browser problem.

--Vic