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.
DOM problems

DOM problems

2003-01-26       - By Ron Rothblum
Reply:     1     2     3     4     5  


The feature you mentioned is set to false and I still get the exception.
The stack trace is:
org.xml.sax.SAXNotRecognizedException:
http://apache.org/xml/properties/dom/current-element-node
     at
org.apache.xerces.parsers.DOMParser.getProperty(DOMParser.java:496)
     at
com.ibm.amit.parser.DOMLineParser.startDocument(DOMLineParser.java:71)
     at
org.apache.xerces.impl.xs.XMLSchemaValidator.startDocument(XMLSchemaValidator
.java:457)
     at
org.apache.xerces.impl.XMLNamespaceBinder.startDocument(XMLNamespaceBinder.java
:444)
     at
org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(XMLDTDValidator.java
:714)
     at
org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity
(XMLDocumentScannerImpl.java:417)
     at
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:813)
     at
org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(XMLEntityManager
.java:676)
     at
org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource
(XMLDocumentScannerImpl.java:252)
     at
org.apache.xerces.parsers.StandardParserConfiguration.parse
(StandardParserConfiguration.java:499)
     at
org.apache.xerces.parsers.StandardParserConfiguration.parse
(StandardParserConfiguration.java:581)
     at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147)
     at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:221)
     at com.ibm.amit.parser.Parser.toDomTree(Parser.java:122)
     at com.ibm.amit.parser.Parser.parse(Parser.java:86)
     at com.ibm.amit.adi.parser.AdiParser.main(AdiParser.java:1197)

does anyone have any other ideas why I can't use this property?

Ron.

>> 1) for some reason when I call the method:
>> 'getProperty("http://apache.org/xml/properties/dom/current-element-node
");'
>> (in the DOMParser class)
>> I get a:"org.xml.sax.SAXNotRecognizedException:

> You are using deferred DOM (read the error message you are getting).
> The property is only supported when
> "http://apache.org/xml/features/dom/defer-node-expansion" is set to
> false.






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