Recent changes to bugs

#7 Parameterized absolute URL expression resolved incorrectly

Srinivas Rao — Mon, 27 Nov 2017 19:50:20 -0000

This fails, if url is pointing to an xsl file and that intern has include to an another xsl file, it could not resolve. This happens even in servingxml 1.1.2. Please let me know if there is any alternate for this problem.

SQL query with empty result set should not throw exception

Anonymous — Fri, 22 Feb 2013 20:48:35 -0000

In a SQL query returns zero result rows, I get an exception:
Flow is null at
com.servingxml.components.recordmapping.GenerateElement.groupStopped(GenerateElement.java:155)
I'd consider this situation as normal and would expect just an empty output but no exception.
This can be done by simply commenting out this code:
154 /* TGE
155 if (flow == null) {
156 throw new ServingXmlException("Flow is null");
157 }
158 */
I have been using the modified code for quite a while w/o any problems so far.

ATFX in Examples should be ATF

wfay — Wed, 27 Feb 2008 16:50:45 -0000

From Examples page:
Converting a CSV file to XML with Record Validation (countries-validated)

code,name
ATFX,"FRENCH SOUTHERN TERRITORIES, D.R. OF"
VUT,VANUATU
WLF,WALLIS & FUTUNA ISLANDS

Should be:
code,name
ATF,"FRENCH SOUTHERN TERRITORIES, D.R. OF"

Choose.java not doing testing in createString()

Gordon Zhang — Fri, 02 Nov 2007 13:57:32 -0000

In version 0.8.0, The Choose class's createString() method is not testing the Alternative's conditions before using its value, as result, the first value is always used.

The code should be

public String createString(ServiceContext context, Flow flow, Record variables, Name variableName) {
String s = null;
for (int i = 0; s == null && i < alternatives.length; ++i) {
Alternative alternative = alternatives[i];
if (alternative.test(context, flow))
s = alternative.createString(context, flow, variables, variableName);
}
return s == null ? "" : s;
}

Notice the missing if test.

line number tracking incorrect for comment lines

Gordon Zhang — Tue, 16 Oct 2007 19:45:45 -0000

The line number tracking in FlatRecordReceiverImpl does not account for the comment lines because FlatRecordReceiverAdapter silently eats comment line without letting FlatRecordReceiverImpl having a chance to update the line number.

"" at start of field read as escaped quote

Daniel Parker — Thu, 16 Aug 2007 12:36:26 -0000

"e";"f";"";"h"

The third value is read as ", as if it was an escaped quote.

The fix is as follows:

Change all occurances of

int n = quoteSymbol.checkEscapeBeforeQuoteSymbol(data, start+currentIndex, end-currentIndex);

int n = 0;
if (inQuotes) {
n = quoteSymbol.checkEscapeBeforeQuoteSymbol(data, start+currentIndex, end-currentIndex);
}

in the following files: RepeatingTaggedFieldReader, SimpleDataBuffer (occurs twice), DelimitedRepeatingGroupReader, DelimitedRepeatingSegmentReader,

Also, change the two occurances of

if (quoteSymbol.checkEscapeBeforeQuoteSymbol(recordBuffer,bytesBuilder)) {

if (quoteState && quoteSymbol.checkEscapeBeforeQuoteSymbol(recordBuffer,bytesBuilder)) {

in DelimitedFlatFileScanner.

sx:choose does not accept sx:fieldAttributeMap descendents

Daniel Parker — Wed, 20 Jun 2007 03:06:30 -0000

Support for sx:choose in sx:recordMapping sections was introduced in 0.6.5. In literal content and element map sections, however, sx:choose still does not accept sx:fieldAttributeMap elements as children of sx:when.

One parameter name appearing more than once in test fails

Daniel Parker — Tue, 19 Jun 2007 03:26:50 -0000

The same parameter name appearing two or more times in a test expression results in a load-time error, e.g. the following statement will fail:

<sx:choose>
<sx:when test="$product='Cap' or $product='Floor'">
<option>
<sx:toString value="{recordType}"/>
</option>
</sx:when>
</sx:choose>

Non-delimited binary datasets with repeating groups fails

Daniel Parker — Thu, 14 Jun 2007 05:08:36 -0000

When reading non-delimited binary datasets, current versions require that the size of the record to be read must be precomputed. This fails when the record contains fixed repeating groups whose number is not known before reading the dataset.

sx:choose inside sx:recordContent fails

Daniel Parker — Thu, 14 Jun 2007 02:47:28 -0000

A defect was inadvertently introduced into the 0.6.5 and later releases.

The issue is with the sx:choose within the sx:recordContent section. With the 0.6.5 release, sx:choose was made to support the contracts for record mapping elements, to allow its use inside sx:recordMapping sections. This leads to a problem for an sx:recordContent that contains an sx:choose, since the sx:choose now looks to it like a sx:recordMapping.

There is a simple work around. Just wrap the record readers and filters appearing in an sx:recordContent element with an sx:recordStream element, i.e. instead of

<sx:recordContent id="123" name="data">
<sx:flatFileReader>
<sx:flatFile ref="juliens"/>
</sx:flatFileReader>
<sx:choose>
<sx:when ...
<sx:when ...
</sx:choose>
<sx:recordMapping ref="datamapping"/>
</sx:recordContent>

use

<sx:recordContent id="123" name="data">
<sx:recordStream>
<sx:flatFileReader>
<sx:flatFile ref="juliens"/>
</sx:flatFileReader>
<sx:choose>
<sx:when ...
<sx:when ...
</sx:choose>
</sx:recordStream>
<sx:recordMapping ref="datamapping"/>
</sx:recordContent>