On 28/02/2011 09:32, Christophe Marchand wrote:
Hi Michael,

I consider moving from JAXP/DOM to ???/S9API the whole content of my project (1200 classes, 250.000 lines, 300 XSL). I use lots of XPath 2.0 instructions. As it will be a huge job, in terms of code & Q/A, I am quite cautious...

I still have some questions :
The s9api interface is designed primarily for controlling XSLT, XQuery, and XPath processing; it is not designed as a tree-navigation interface to compete with DOM. Equally, the Saxon NodeInfo interface for tree navigation is designed primarily to support the needs of XPath etc, not for direct use by applications. If you want to manipulate XML using a procedural, navigational API then I would recommend XOM. Saxon and s9api will interwork with XOM very comfortably. Ideally, though, my recommendation would be to avoid low-level XML processing in Java, in favour of implementing as much as possible of your application using XSLT and XQuery.

Michael Kay

Solved issues are :

Thanks a lot in advance,
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ saxon-help mailing list archived at http://saxon.markmail.org/ saxon-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/saxon-help