Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Updated: (XERCESJ-1178) Error getting prefix for an attribute with no nam

Updated: (XERCESJ-1178) Error getting prefix for an attribute with no nam

2006-08-21       - By hua lei (JIRA)
Reply:     1     2     3  

    [ http://issues.apache.org/jira/browse/XERCESJ-1178?page=all ]

hua lei updated XERCESJ-1178:
-----------------------------

   Attachment: stax_patch_8.20.zip

The stack underflowing is fixed.

>The other issue is with the AsyncSAXParser thread. It seems like it never
>terminates. I noticed that because the JVM wasn't exiting at the end of my
>test program. I've made it a daemon thread so that the JVM exits but
>there's still a threading problem there. Perhaps the call to the parse
>method on the XMLReader never returns?

In two cases, the AsyncSAXParser thread will not teminate.
1) There is an exception occures in the SAXXMLStreamReaderImpl
2) The user doesn't parse the document to the end

To make sure the AsyncSAXParser thread terminates correctly, following
modifications are done.
1)  When an exception occurs in the next() method the AsyncSAXParser thread is
interrupted, because after that no call to the StreamReader is valid.
2)  When an exception occures in other methods of StreamReader, a call to
StreamReader may still be valid, so the AsyncSAXParser thread shouldn't be
interrupted in this case.
3) In the close() method, if the AsyncSAXParser thread is still alive,
interrupt it.
But if the user doesn't close the StreamReader after using it, the
AsyncSAXParser thread may never terminate. So user should call the close()
method.


>In the fix that you made in SAXXMLStreamReader.initialElementAttrs() you
>added a check for duplicate attributes that I didn't understand. A SAX
>parser already does this well-formedness check. Is there a reason for
>doing that again in the XMLStreamReader?

The SAX parser cann't recognize the element such as  "<root xmlns:a='xxx' xmlns
:b='xxx' a:attr='1' b:attr='2' />", so I  check it myself.



> Error getting prefix for an attribute with no namespace
> -------------------------------------------------------
>
>                 Key: XERCESJ-1178
>                 URL: http://issues.apache.org/jira/browse/XERCESJ-1178
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: StAX
>    Affects Versions: 2.8.0
>            Reporter: Lucian Holland
>         Assigned To: Michael Glavassevich
>         Attachments: stax_patch_8.19.zip, stax_patch_8.20.zip
>
>
> The initialElementAttrs()  method of SAXXMLStreamReader sets the prefix of
attributes to null if it finds no colon in the attribute name; the problem with
this is that getAttributeNamespace() uses this prefix when looking up the
namespace uri with a call to getNamespaceURI on the NamespaceContextImpl, and
this method throws an IllegalArgumentException if null is passed in.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http:/
/issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)