XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

In Nux validation and XQuery are completely separate features. Nux is  
not W3C Schema aware (Saxon-SA is).

Right now, you'd have to update the data, then serialize to a  
temporary ByteArrayOutputStream, then reparse from an  
ByteArrayInputStream with schema validation enabled, using an  
appropriate Builder (e.g. taken from a BuilderPool).

And if your source is a DOM, you'd have to additional convert DOM ->  
XOM -> DOM using the DOMConverter. It works, but is clearly far from  
ideal, in light of the cumbersome conversions involved...

Or you could try using Saxon-SA.

> I was wondering if Saxon with JAXP 1.3 can  be useful.(I am yet to  
> catch up with these two as well).

Potentially yes, but if you'd like to stick with XOM, you'd have to  
write yourself a JAXP 1.3 provider that works over XOM, rather than  
DOM or similar. I'm not aware of anyone that has done that yet.

Wolfgang.

On Aug 10, 2005, at 3:47 PM, vitrpp AT netscape.net wrote:

> Although I am new to XOM it caught my attention by the inplace  
> update and validtion feature. I am currently looking for a way to  
> update a DOM using XQuery (where the in place update feature can  
> help) but want to make sure that the updates are validated (adheres  
> to the associated schema).
> This means I need a way to associate a complex type (on a finer  
> granularity) with the node(s) that I will fetch using the XQuery  
> before morphing them.
> Can some one suggest a way of doing it.
> One way we follow is to walk the Content Model provided by Abstract  
> Schema implemenation before updating the DOM. But I am looking for  
> something elegant and widely used solution.
> I was wondering if Saxon with JAXP 1.3 can  be useful.(I am yet to  
> catch up with these two as well).
>
> Can some one share some information?
>
> many thanks