RES: 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

RES: Node Info and PSVI in one parser

RES: Node Info and PSVI in one parser

2003-10-08 - By Rubens Del Monte

My test was wrong ! I used a loop to print all values, and everything was
null, but there was an if that shown only the element nodes, and the values
are in the text nodes

It will work fine ! thanks max !

-----Mensagem original-----
De: Maksym Kovalenko [mailto:mkovalenko@(protected)]
Enviada em: quarta-feira, 8 de outubro de 2003 15:40
Para: xerces-j-user@(protected)
Assunto: Re: Node Info and PSVI in one parser

According to specification nodeValue is null for elements.
http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030609/core.html#ID-F68D080
<http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030609/core.html#ID-F68D080
>

What did you expect to receive from getNodeValue()?

Max

Rubens Del Monte wrote:

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"
<http://apache.org/xml/properties/internal/grammar-pool> ,grammarPool);
DOMParser parser = new DOMParser(config);
parser.setFeature( "http://xml.org/sax/features/validation"
<http://xml.org/sax/features/validation> ,true);
parser.setFeature(
"http://apache.org/xml/features/validation/schema"
<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"
<http://xml.org/sax/features/validation> ,true);
parser.setFeature( "http://apache.org/xml/features/validation/schema"
<http://apache.org/xml/features/validation/schema> ,true);
parser.setProperty(
"http://apache.org/xml/properties/dom/document-class-name"
<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

--

_____

Maksym Kovalenko
Software Engineer
Marketswitch Corporation
http://www.marketswitch.com <http://www.marketswitch.com/>
108 Powers Court, Suite 225
Dulles, VA 20166
Phone: +1 (703) 444-6750 ext. 302
Fax: +1 (703) 444-6812

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<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)">
<link rel=Edit-Time-Data href="cid:editdata.mso@(protected)">

<title> </title>

<style>

</style>

</head>

<body bgcolor=white lang=PT-BR link=blue vlink=purple style='tab-interval:35
.4pt'>

<div class=Section1>

My test was wrong
! I used a loop to print all values, and everything was null, but there was an
if that shown only the element nodes, and the values are in the text nodes&
#8230;<o:p></o:p>

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

It will work fine
! thanks max !<o:p></o:p>

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

-----Mensagem
original----- 
De: Maksym Kovalenko
[mailto:mkovalenko@(protected)] 
Enviada em: quarta-feira, 8 de
outubro de 2003 15:40 
Para: xerces-j-user@(protected)
 
Assunto: Re: Node Info and PSVI in
one parser<o:p></o:p>

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

According to specification nodeValue is null for elements. 
<a
href="http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030609/core.html#ID
-F68D080">http:/
/www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030609/core.html#ID-F68D080</a> 
 
What did you expect to receive from getNodeValue()? 
 
Max 
 
Rubens Del Monte wrote: 
<![if !supportLineBreakNewLine]> 
<![endif]><o:p></o:p>

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

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

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


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

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

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

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

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

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

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

            <u3:p
></u3:p><o:p></o:p>

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

<u3:p></u3:p>   In this one, I can acess the PSVI but not
the node’s value :<u3:p></u3:p><o:p></o:p>

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


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


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


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


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


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

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


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

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

<u3:p></u3:p><u3:p></u3:p>I could parse the document
twice,
using the normal way and the PSVI, but it would take more time and resources&
#8230;<u3:p></u3:p><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. <u3:p></u3:p><o:p></o:p>

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

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

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

-- 
<![if !supportLineBreakNewLine]> 
<![endif]><o:p></o:p>



<div class=MsoNormal align=center style='margin-left:38.85pt;text-align:center'
>

<hr size=2 width="100%" align=center>

</div>

Maksym Kovalenko 
Software Engineer 
Marketswitch Corporation 
<a href="http://www.marketswitch.com/">
http://www.marketswitch
.com</a> 
108 Powers Court, Suite 225 
Dulles, VA 20166 
Phone: +1 (703) 444-6750 ext. 302 
Fax: +1 (703) 444-6812<o:p></o:p>

</div>

</body>

</html>