Custom XML Validation

View: New views
3 Messages — Rating Filter:   Alert me  

Custom XML Validation

by Kyle Cunningham-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi –

 

I’m writing an XMLValidator tool that first parses a file against the schema (using Xerces) then runs custom xml checks if the build was successful.  I’m using a SAXBuilder for this and just calling the build() method to parse the XML document.  The additional checks include things like making sure the content of required elements is present, etc (I couldn’t find a way to specify this in an XML schema).

 

My problem is that I am not able to determine the line number a “problem” element lives at within the xml document when I encounter something in the additional processing routine. 

 

I tried throwing a SAXParseException and calling the getLineNumber() method, but the exception seems to have no knowledge of the document.  I also read some stuff about using a SAXHandler and setting the document location, but I couldn’t really get my head around it enough to understand how I could use it.  I’m fairly new to JDOM.  Is there any easy way to accomplish this?

 

Thanks for your time.

 

Kyle

 

 

 

 

 

 

 


_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/youraddr@...

Re: Custom XML Validation

by Per Norrman-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

jdom-contrib, http://jdom.org/dist/binary/jdom-contrib-1.0.zip, contains
an example of how to extend SAXBuilder and Element in order to attach line
number information. Look for LineNumberSAXBuilderDemo in the samples
directory.

/per

Kyle Cunningham skrev:

> Hi –
>
>  
>
> I’m writing an XMLValidator tool that first parses a file against the
> schema (using Xerces) then runs custom xml checks if the build was
> successful.  I’m using a SAXBuilder for this and just calling the
> build() method to parse the XML document.  The additional checks include
> things like making sure the content of required elements is present, etc
> (I couldn’t find a way to specify this in an XML schema).
>
>  
>
> My problem is that I am not able to determine the line number a
> “problem” element lives at within the xml document when I encounter
> something in the additional processing routine.
>
>  
>
> I tried throwing a SAXParseException and calling the getLineNumber()
> method, but the exception seems to have no knowledge of the document.  I
> also read some stuff about using a SAXHandler and setting the document
> location, but I couldn’t really get my head around it enough to
> understand how I could use it.  I’m fairly new to JDOM.  Is there any
> easy way to accomplish this?
>
>  
>
> Thanks for your time.
>
>  
>
> Kyle
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/youraddr@...

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/youraddr@...

[ANN]VTD-XML 2.7

by anon_anon :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

VTD-XML 2.7 is released and can be downloaded at
http://sourceforge.net/projects/vtd-xml/files/

Below is a summary of what are the new features and enhancements.

Expanded VTD-XML's Core API

* VTDNav: toStringUpperCase, toStringLowerCase, contains(), endsWith(),
startsWith()
* Extended VTD added in-memory buffer support

Improved Xpath

* added the following XPath 2.0 functions: abs(), ends-with(), upper-case(),
lower-case()
* added support for variable reference
* significantly enhanced XPath syntax, checking error reporting (Special
thanks to Mark Swanson)
* Internal performance tuning

Bug fixes and Code Enhancement

* C version significantly removed warning message, fix memory leak during
Xpath expression parsing,
* Various bug fies (Special thanks to Jon Roberts, John Zhu, Matej Spiller,
Steve Polson, and Romain La Tellier)

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/youraddr@...