Recent changes to bugs

error in reported as in

2011-08-17T13:24:56Z

I typed this code, there's an error at the first line - the for-each tag is accidentally closed there.

<xsl:for-each select="./qualifier='author']" />
<xsl:value-of select="./node()"/><xsl:text>, </xsl:text>
</xsl:for-each>

That threw the following exception (line 443 is the third line here with the closing tag):

org.xml.sax.SAXParseException: The element type "xsl:if" must be terminated by the matching end-tag "</xsl:if>".
context:/jndi:/localhost/themes/abc/def.xsl - 443:23

The Exception talks about xsl:if, while this really was an xsl:for-each.

Maybe just this exception message needs to be fixed, maybe this points to some other underlying problem or maybe this is really nothing. I'm not really sure if this is a bug but I thought I'll report it anyway.

I was using XSL 1.0 in Apache Cocoon in DSpace, version is probably customized cocoon-core 2.2.0.

XML 1.1 parser error

2011-02-14T17:44:07Z

Opening this bug again, because I have no ability to own or edit 3181061.

The XML parser is getting attribute values that are wrong (not what is in the document) under certain circumstances. I've attached an XML file and a simple program that reproduce the problem.

The problem only occurs on Java 1.6 using the SAX parser shipped with it.

The XML file provided must be used without any editing. Removing some "unnecessary" and unrelated tags will result in different (and sometime correct) behavior. Also, switching the XML version number from 1.1 to 1.0 results in correct behavior. Even removing the commented out XML results in the correct behavior. I tried to make the XML file as small as possible, but found if I removed any more content, then the parser behaves correctly.

I was not able to step through the DOM Parser with the debugger to determine where the problem is occurring or why.

I submitted this first to Oracle, but seem to have been ignored (perhaps because they do not support the SAX parser).

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run the sample code provided with sample XML file.

You'll see that in the last line, the fill, gridHeight, gridWidth, gridX, gridY, ipadX, and ipadY attributes are wrong.

Note: You may need to change the package name and path to the XML file to match your setup.

EXPECTED VERSUS ACTUAL BEHAVIOR :
(The output will show twice, as I run through the DOM parser (which uses the SAX parser, I believe) and then the SAX parser directly.
EXPECTED -
Node: GridBagConstraints : anchor = 10; fill = 2; gridHeight = 1; gridWidth = 0; gridX = 0; gridY = 8; insetsBottom = 0; insetsLeft = 0; insetsRight = 0; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 18; fill = 2; gridHeight = 1; gridWidth = 0; gridX = 0; gridY = 0; insetsBottom = 0; insetsLeft = 0; insetsRight = 0; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 1.0; weightY = 1.0;
Node: GridBagConstraints : anchor = 13; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 1; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 17; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 2; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 40; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 13; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 5; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 17; fill = 0; gridHeight = 1; gridWidth = 0; gridX = 6; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;

ACTUAL -
Node: GridBagConstraints : anchor = 10; fill = 2; gridHeight = 1; gridWidth = 0; gridX = 0; gridY = 8; insetsBottom = 0; insetsLeft = 0; insetsRight = 0; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 18; fill = 2; gridHeight = 1; gridWidth = 0; gridX = 0; gridY = 0; insetsBottom = 0; insetsLeft = 0; insetsRight = 0; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 1.0; weightY = 1.0;
Node: GridBagConstraints : anchor = 13; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 1; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 17; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 2; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 40; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 13; fill = 0; gridHeight = 1; gridWidth = 1; gridX = 5; gridY = 25; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = 0; ipadY = 0; weightX = 0.0; weightY = 0.0;
Node: GridBagConstraints : anchor = 17; fill = B; gridHeight = e; gridWidth = m; gridX = .; gridY = mo; insetsBottom = 0; insetsLeft = 0; insetsRight = 5; insetsTop = 0; ipadX = G; ipadY = s; weightX = 0.0; weightY = 0.0;

REPRODUCIBILITY :
This bug can be reproduced always.

XML 1.1 parser error

2011-02-14T17:36:46Z

The XML parser is getting attribute values that are wrong (not what is in the document) under certain circumstances. I've attached an XML file and a simple program that reproduce the problem.

The problem only occurs on Java 1.6 using the SAX parser shipped with it.

I was not able to step through the DOM Parser with the debugger to determine where the problem is occurring or why.

I submitted this first to Oracle, but seem to have been ignored (perhaps because they do not support the SAX parser).

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run the sample code provided with sample XML file.

You'll see that in the last line, the fill, gridHeight, gridWidth, gridX, gridY, ipadX, and ipadY attributes are wrong.

Note: You may need to change the package name and path to the XML file to match your setup.

REPRODUCIBILITY :
This bug can be reproduced always.

Pascal link broken

2009-02-07T05:42:09Z

on the page
http://www.saxproject.org/langs.html

The pascal link is broken

http://xml.defined.net/SAX
Pascal, with a Delphi focus. Version 1.1 is done, supports SAX2r2.

Error Handler Attribute Validation

2009-02-03T20:59:36Z

For my SAX Parser class that implements the DefaultHandler, it was noticed that the attribute validation happens while the startElement points to its parent element.

XML File snippet:
<featureRules xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FSORulesSchema.xsd">
<featureSet marketCode="" modelYear="2004" featureCode="" >
<rule id="4895" operationType="A">
<featureValue>Yes</featureValue>
<startDate>1967-08-13</startDate>

XSL File Snippet :
<xs:element name="featureRules">
<xs:complexType>
<xs:sequence>
<xs:element ref="featureSet" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="featureSet">
<xs:complexType>
<xs:sequence>
<xs:element ref="rule" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="marketCode" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="NA"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="modelYear" type="xs:short" use="required"/>
<xs:attribute name="featureCode" type="xs:string" use="required"/>

Console Output :
(note : Element name is printed from error() of ErrorHandler. remaining is printed in the startElement() )

Start Local Name : featureRules
Attribute name : xsi:noNamespaceSchemaLocation
Attribute value : FSORulesSchema.xsd
Element name : featureRules
cvc-enumeration-valid: Value '' is not facet-valid with respect to enumeration '[NA]'. It must be a value from the enumeration.
Element name : featureRules
cvc-attribute.3: The value '' of attribute 'marketCode' on element 'featureSet' is not valid with respect to its type, 'null'.
Start Local Name : featureSet
Attribute name : marketCode
Attribute value :
Attribute name : modelYear
Attribute value : 2004
Attribute name : featureCode
Attribute value :

Thanks,
Aneesh

inconsistent postconditions in org.xml.sax.Attributes

2008-03-20T12:36:44Z

(javadoc shipped with Java 6)

class org.xml.sax.Attributes

specification for method getValue(String qName) and getType(String qName) say they return: "(...) null (...) if the attribute is not in the list or if qualified names are not available."

However, getIndex(String qName) returns "The index of the attribute, or -1 if it does not appear in the list." It does not state that null is returned when qualified names are not available.

Suggested fix: documentation for getIndex(String qName) should say "Returns: The index of the attribute, or -1 if it does not appear in the list, or if or if qualified names are not available" (I think it is the expected behaviour).

SAX fails to read character entity

2007-06-19T11:22:45Z

Hi,

when using SAX via JAXP the following code throws a org.xml.sax.SAXParseException: Character reference "&#xB" is an invalid XML character

DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = factory.newDocumentBuilder();

Document doc = docBuilder.parse(new ByteArrayInputStream("<?xml version='1.0' encoding='UTF-8'?><tag>something</tag>".getBytes()) );

But the character entity  is valid according to the original XML 1.0 spec. It works however if I change the XML Version to 1.1, but the XML 1.1 spec has not really changed at that point.

See:
http://www.w3.org/TR/1998/REC-xml-19980210#sec-references
http://www.w3.org/TR/xml11/#sec-references

Concerning the plattform and versions: Im using WinXP Prof. and a Java 6 JDK (version: build 1.6.0_01-b06). I dont know how to get the SAX version, but I figured the serialVersionUID of the thrown SAXParseException: -5651165872476709336

cheers,
joachim

InputSource character buffer size 2048 problem

2006-08-11T16:36:41Z

I suppose someone has submitted this bug already. when
the characters content is across two "chunks of
character buffer", the content will be split into two...

please follow... if anyone wants to =P

website not up:http://xml.org/sax/properties/lexical-handler

2006-06-16T17:35:12Z

This website is not working:
http://xml.org/sax/properties/lexical-handler

InputSource character buffer size 2048 problem

2006-03-05T23:53:22Z

I parse a XML document with SAX2 via InputSource:

myParser.parse(new InputSource(xmlFile.toURL
().openStream()));

I get a tag's value splitted into two parts using the
callback "public void characters(...)". The first part
is in the character array on position 2044 with length
4 "16.0" and the second part "5.2005" on position 0
with length 6. It should be a German date
value "16.05.2005" if receiving in one part.
This behavior is other than in SAX1 parsers. It seams
to relate to the character array size 2048? Ho can I
avoid this splitting?