Node Info and PSVI in one parser

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

Node Info and PSVI in one parser

Node Info and PSVI in one parser

2003-10-08 - By Rubens Del Monte

Reply: 1 2

Hello,

My problem is that I can´t acess both PSVI and the node´s value in the
same parse.

In this code bellow, I can acess the node information but I could only
acess top-level PSVI with the XSModel returned.

XMLParserConfiguration config = new StandardParserConfiguration();

config.setProperty("http://apache.org/xml/properties/internal/grammar-pool",
grammarPool);
DOMParser parser = new DOMParser(config);

parser.setFeature("http://xml.org/sax/features/validation",true);

parser.setFeature("http://apache.org/xml/features/validation/schema",true);
parser.parse(filename);
doc = parser.getDocument();

org.apache.xerces.impl.xs.psvi.XSModel model =
grammarPool.toXSModel();

In this one, I can acess the PSVI but not the nodes value :

DOMParser parser = new DOMParser();
parser.setFeature("http://xml.org/sax/features/validation",true);

parser.setFeature("http://apache.org/xml/features/validation/schema",true);

parser.setProperty("http://apache.org/xml/properties/dom/document-class-name
","org.apache.xerces.dom.PSVIDocumentImpl");
parser.parse(filename);
doc = parser.getDocument();

// only to test
ElementPSVI elem = (ElementPSVI) node;
System.out.println(node.getNodeName() + " : "+node.getNodeValue()); //
the output is always : node name : null;

I could parse the document twice, using the normal way and the PSVI, but it
would take more time and resources
Sorry to keep bothering you but I´ve read all the FAQ and went trought the
docs but I still haven´t found a way to solve this.

Thank´s

Rubens

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft
-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http:
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 9">
<meta name=Originator content="Microsoft Word 9">
<link rel=File-List href="cid:filelist.xml@(protected)">

<style>

</style>
</head>

<body lang=PT-BR style='tab-interval:35.4pt'>

<div class=Section1>

Hello,
<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

   My problem is that I can´t acess both PSVI and the
node´s value in the same parse.<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

   In this code
bellow,
I can acess the node information but I could only acess top-level PSVI with the
XSModel returned.
<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

XMLParserConfiguration config = new
StandardParserConfiguration();<o:p></o:p>

           
config.setProperty("http://apache.org/xml/properties/internal
/grammar-pool",grammarPool);<o:p></o:p>

           
DOMParser parser = new DOMParser(config);<o:p></o:p>

           
parser.setFeature("http://xml.org/sax/features/validation"
,true);<o:p></o:p>

           
parser.setFeature("http://apache.org/xml/features/validation/schema
",true);<o:p></o:p>

           
parser.parse(filename);<o:p></o:p>

           
doc = parser.getDocument();<o:p></o:p>

            
<o:p></o:p>

           
org.apache.xerces.impl.xs.psvi.XSModel model = grammarPool.toXSModel();
  <o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

   In this one, I can acess the PSVI but not the node&
#8217;s value
:<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

   DOMParser parser = new DOMParser();<o:p></o:p>

   parser.setFeature("http://xml.org/sax/features
/validation",true);<o:p></o:p>

   parser.setFeature("http://apache.org/xml/features
/validation/schema",true);<o:p></o:p>

   parser.setProperty("http://apache.org/xml
/properties/dom/document-class-name","org.apache.xerces.dom
.PSVIDocumentImpl");<o:p></o:p>

   parser.parse(filename);<o:p></o:p>

   doc = parser.getDocument();<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

   // only to test<o:p></o:p>

   ElementPSVI elem = (ElementPSVI) node;<o:p></o:p>

   System.out
.println(node.getNodeName()
+ " : "+node.getNodeValue()); // the output is always : “ node
name :
null”;<o:p></o:p>

<![if !supportEmptyParas]>
 <![endif]><o:p></o:p>

<![if
!supportEmptyParas]> <![endif]><o:p></o:p>

I could parse the
document twice, using the normal way and the PSVI, but it would take more time
and resources…<o:p></o:p>

Sorry to keep
bothering
you but I´ve read all the FAQ and went trought the docs but I still haven´t
found
a way to solve this. <o:p></o:p>

<![if
!supportEmptyParas]> <![endif]><o:p></o:p>

Thank´s<o:p></o:p>

<![if
!supportEmptyParas]> <![endif]><o:p></o:p>

Rubens<o:p></o:p>

</div>

</body>

</html>