On Wed, 7 Aug 2002 16:27:02 +0200
Jeroen Breedveld [EMAIL PROTECTED] wrote:
| Oh,
|
| Why this code ?
|
| System.setProperty
| (org.infozone.tools.xml.queries.XPathQueryFactory,
| org.infozone.tools.xml.queries.xalan2.XPathQueryFactoryImpl);
|
| 1. It only set up XPath, not XUpdate ! Right ?
This code is used to tell Lexus which XPathQueryFactory it has to use to
select the nodes in XUpdate queries. By default this is Xalan so if you
use that you don't have to set anything. If you supply Lexus with
another DOM implementation document you (may) have to supply your own
XPathQueryFactory, for example if Lexus is used with X-Hive/DB you do
this:
System.setProperty(org.infozone.tools.xml.queries.XPathQueryFactory,
com.xhive.xupdate.XhiveXPathQueryFactory);
| 2. Does this version of XPath is better than the Xalan one ?
There's probably no difference because it is a wrapper around the
Xalan's XPathQueryFactory, but there are probably other people on this
list that can answer this question better...
Absolutely right, Jeroen.
As far as we don't have a common XPath factory (JAXP or something similar)
we need a way to make the used XPath implementation pluggable. The package
infozone.tools simply provides such a factory for XPath implementations
like JAXP provides factories for SAXParser, DocumentBuilder etc. But this
package doesn't contain any XPath/XUpdate implementation specific stuff.
Lars.
--
__
Lars Martin mailto:[EMAIL PROTECTED]
SMB GmbHhttp://www.smb-tec.com
--
Post a message: mailto:[EMAIL PROTECTED]
Unsubscribe:mailto:[EMAIL PROTECTED]
Contact administrator: mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
--
