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-21       - By Shital Joshi
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

hi there,

I tried setting this property:

parser.setFeature( "http://apache.org/xml/features/dom/defer-node-expansion"
,false);

But it gives me SAXNotSupportedException. I am using Xercers-j 2.4. Any
ideas why?

-Shital Joshi
MFG Systems



-----Original Message-----
From: Doug Helton [mailto:dhelton@(protected)]
Sent: Wednesday, May 21, 2003 10:42 AM
To: xerces-j-user@(protected)
Subject: RE: XML parser


Shital,
  If you are trying to get this just to debug, you can get the line number of
the error from the exception, which usually puts you at the end of the
element that has the error.  If you are trying to display the name for users
you will probably have to follow Ragunath's suggestion or what you planned
would work as well.

Doug

-----Original Message-----
From: Ragunath Marudhachalam [mailto:rmarudhachalam@(protected)]
Sent: Wednesday, May 21, 2003 10:28 AM
To: xerces-j-user@(protected)
Subject: RE: XML parser


You have to set

parser.setFeature( "http://apache.org/xml/features/dom/defer-node-expansion"
,false);

and in the errorhandler's callback function,

Element node =
(Element)parser.getProperty("http://apache.org/xml/properties/dom/current-el
ement-node");

  if (node != null)
               System.out.println(node.getNodeName());


Ragu
CircuitVision



-----Original Message-----
From: Shital Joshi [mailto:shital@(protected)]
Sent: Wednesday, May 21, 2003 10:19 AM
To: xerces-j-user@(protected)
Subject: RE: XML parser


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?

-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)


---------------------------------------------------------------------
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)