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.
XML parser

XML parser

2003-05-22       - By K. Venugopal
Reply:     1     2     3     4     5     6     7     8     9     10     >>  



Shital Joshi wrote:

>hi there,
>
>If I am using SAX Parser + schema to validate the XML document, can I still
>get the name of element where schema validation failed? I guess I have to
>implement startElement() method and in the errorHandler I can get the
>current element name from the startElement() method. Is this a correct
>approach?
>
Yes thats right .
Regards
venu

>
>-Shital Joshi
>MFG Systems
>
>
>
>-----Original Message-----
>From: K. Venugopal [mailto:k.venugopal@(protected)]
>Sent: Tuesday, May 20, 2003 5:26 AM
>To: xerces-j-user@(protected)
>Subject: Re: XML parser
>
>
>Hi Utsav ,
>
>With  xerces you could get the location where error has occured . For
>this you need to set a error handler and query the current
>node in the error handler as shown below .
>
>eg:
>       Element node =
>(Element)parser.getProperty("http://apache.org/xml/properties/dom/current-el
>ement-node");
>
>For more information refer to
>http://xml.apache.org/xerces2-j/properties.html
>
>Hope this helps .
>
>Regards
>venu
>
>  
>
>>Hi,
>>   Presently I am working on a project whose aim is to validify an
>>invalid XML document. For it, I need a XML validating parser, to which I
>>call from my Java program giving it the root of the DOM tree of the XML
>>document and it should return to the program , the pointer to the node
>>which contains the error (if the document is invalid) and NULL (if the
>>document is valid). Does any such parser exits ? or, is there any parser
>>available to which I can easily modify to get the desired ersult.
>>
>>Utsav
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
>>For additional commands, e-mail: xerces-j-user-help@(protected)
>>
>>
>>
>>    
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
>For additional commands, e-mail: xerces-j-user-help@(protected)
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
>For additional commands, e-mail: xerces-j-user-help@(protected)
>
>  
>


<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <title></title>
</head>
<body>
<br>
<br>
Shital Joshi wrote:<br>
<blockquote type="cite"
cite="mid003e01c31fa3$ef40af70$2dc809c0@(protected)">
 <pre wrap="">hi there,

If I am using SAX Parser + schema to validate the XML document, can I still
get the name of element where schema validation failed? I guess I have to
implement startElement() method and in the errorHandler I can get the
current element name from the startElement() method. Is this a correct
approach?</pre>
</blockquote>
Yes thats right . <br>
Regards<br>
venu<br>
<br>
<blockquote type="cite"
cite="mid003e01c31fa3$ef40af70$2dc809c0@(protected)">
 <pre wrap="">

-Shital Joshi
MFG Systems



-----Original Message-----
From: K. Venugopal [<a class="moz-txt-link-freetext" href="mailto:k.venugopal
@(protected)">mailto:k.venugopal@(protected)</a>]
Sent: Tuesday, May 20, 2003 5:26 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:xerces-j-user@(protected)
.org">xerces-j-user@(protected)</a>
Subject: Re: XML parser


Hi Utsav ,

With  xerces you could get the location where error has occured . For
this you need to set a error handler and query the current
node in the error handler as shown below .

eg:
      Element node =
(Element)parser.getProperty(<a class="moz-txt-link-rfc2396E" href="http:/
/apache.org/xml/properties/dom/current-element-node">"http://apache.org/xml
/properties/dom/current-el
ement-node"</a>);

For more information refer to
<a class="moz-txt-link-freetext" href="http://xml.apache.org/xerces2-j
/properties.html">http://xml.apache.org/xerces2-j/properties.html</a>

Hope this helps .

Regards
venu

 </pre>
 <blockquote type="cite">
   <pre wrap="">Hi,
  Presently I am working on a project whose aim is to validify an
invalid XML document. For it, I need a XML validating parser, to which I
call from my Java program giving it the root of the DOM tree of the XML
document and it should return to the program , the pointer to the node
which contains the error (if the document is invalid) and NULL (if the
document is valid). Does any such parser exits ? or, is there any parser
available to which I can easily modify to get the desired ersult.

Utsav



---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:xerces
-j-user-unsubscribe@(protected)">xerces-j-user-unsubscribe@(protected)</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href=
"mailto:xerces-j-user-help@(protected)">xerces-j-user-help@(protected)</a>



   </pre>
 </blockquote>
 <pre wrap=""><!---->


---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:xerces
-j-user-unsubscribe@(protected)">xerces-j-user-unsubscribe@(protected)</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href=
"mailto:xerces-j-user-help@(protected)">xerces-j-user-help@(protected)</a>



---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:xerces
-j-user-unsubscribe@(protected)">xerces-j-user-unsubscribe@(protected)</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href=
"mailto:xerces-j-user-help@(protected)">xerces-j-user-help@(protected)</a>

 </pre>
</blockquote>
<br>
</body>
</html>