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.
XMLGrammarPreparser question

XMLGrammarPreparser question

2003-09-11       - By Henry Miller
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

I posted this question to xerces-j-dev, but got no response so I'll
try here. Sorry if you've seen it before...

Please. I need an answer from somemone who knows better than I, here goes:


Without setting anything special in the XMLGrammarPreparser,
shouldn't the Xerces parse process automatically resolve external
entities?

I mean, if I were validating an XML instance document using a DTD
that contains externally defined parameter entities, doesn't the
parser automatically resolve the external entities there in order to
validate the document?

So why can't I get the preparser to resolve the same entities, if I
just want to cache the grammar from the same DTD in the example
above? The (pre)parser itself keeps giving me an error of
"EntityNotDeclared" for the only external entity defined in my test.

Has anyone run into this situation?

What am I not telling the XMLGrammarPreparser? I am not setting any
features or properties (actually I tried setting relevant features,
but they seem to be ignored by the parser).

Can someone help me? Any pointers?? I'm running with Xerces-J 2.5.0.


As a footnote to the original question I've posted, here's some
additional info to my problem:

I'm setting features within my preparser object, but they are
definitely being ignored when it runs -- I've even misspelled them
purposely just to see if the code would complain. Same errors as
before resulted, so essentially *nothing* happened. Should I report a
bug in the preparser?

My test code is as follows (much of it borrowed from the
XMLGrammarBuilder.java sample program) :

   SymbolTable sym = new SymbolTable(BIG_PRIME);
   XMLGrammarPreparser preparser = new XMLGrammarPreparser(sym);
   XMLGrammarPoolImpl grammarPool = new XMLGrammarPoolImpl();

   if(isDTD) {

      XMLDTDLoader grammarLoader = new XMLDTDLoader(sym, grammarPool);
      preparser.registerPreparser(XMLGrammarDescription.XML_DTD,
grammarLoader);

   } else {

      preparser.registerPreparser(XMLGrammarDescription.XML_SCHEMA, null);

   }

   preparser.setGrammarPool(grammarPool);
   preparser.setProperty(GRAMMAR_POOL, grammarPool);
   preparser.setProperty(SYMBOL_TABLE, sym);

   preparser.setFeature(NAMESPACES_FEATURE_ID, true);
   preparser.setFeature(VALIDATION_FEATURE_ID, false);
   preparser.setFeature(SCHEMA_VALIDATION_FEATURE_ID, false);

   // Set these to see if preparser will listen to them:

preparser.setFeature("http://xml.org/sax/features/external-parameter-entities",
true);
 preparser.setFeature("http://apache.org/xml/features/continue-after-fatal
-error",
true);

preparser.setFeature("http://apache.org/xml/nonvalidating/load-dtd-grammar",
true);

preparser.setFeature("http://apache.org/xml/nonvalidating/load-external-dtd",
true);

   // parse the grammar...
   Grammar g = null;
   try {
      if (isDTD) {
        // Process DTD input file
        g = preparser.preparseGrammar(XMLGrammarDescription.XML_DTD,
                                      stringToXIS(inputFile) );
      } else {
        // Process schema input file
        g = preparser.preparseGrammar(XMLGrammarDescription.XML_SCHEMA,
                                      stringToXIS(inputFile) );
      }


The problem is with DTDs being read. I get in return the message:

[Error] :-1:-1:
http://www.w3.org/TR/1998/REC-xml-19980210#EntityNotDeclared?CONTACT
[Fatal Error] :-1:-1:
http://www.w3.org/TR/1998/REC-xml-19980210#MSG_OPEN_PAREN_OR_ELEMENT_TYPE
_REQUIRED_IN_CHILDREN?Address

Error found during parsing:
http://www.w3.org/TR/1998/REC-xml-19980210#MSG_OPEN_PAREN_OR_ELEMENT_TYPE
_REQUIRED_IN_CHILDREN?Address

Stack Trace:
:::::-1:-1:http://www.w3.org/TR/1998/REC-xml-19980210#MSG_OPEN_PAREN_OR_ELEMENT
_TYPE_REQUIRED_IN_CHILDREN?Address
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
        at
org.apache.xerces.impl.XMLDTDScannerImpl.scanChildren(Unknown Source)
        at
org.apache.xerces.impl.XMLDTDScannerImpl.scanElementDecl(Unknown
Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source)
        at
org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDExternalSubset(Unknown
Source)
        at org.apache.xerces.impl.dtd.XMLDTDLoader.loadGrammar(Unknown Source)
        at
org.apache.xerces.parsers.XMLGrammarPreparser.preparseGrammar(Unknown
Source)
        at com.eti.rs.xml.XMLParser.main(Unknown Source)

Clearly the preparser stopped before any of my code starts. So what
did I forget to tell the preparser? Or is this really a bug?

Any reply is more than I had before. Thanks for reading this far!
--


--Henry Miller

hmiller@(protected)
Evolutionary Technologies International, Inc.

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