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 ?
2. Does this version of XPath is better than the Xalan one ?
Thanks for the information
Christophe
"Jeroen
Breedveld" To: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED] cc: <[EMAIL PROTECTED]>
ve.com> Subject: RE: BUG in XUpdate
implementation
07/08/2002
15:19
Please
respond to
xindice-users
| -----Original Message-----
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]
| Sent: woensdag 7 augustus 2002 11:21
| To: [EMAIL PROTECTED]
| Subject: RE: BUG in XUpdate implementation
|
|
|
| No problem
|
| For this, I have downloaded the XUpdate reference
| implementation of xmldB
| ( http://www.xmldb.org/xupdate/index.html )
|
| I have import it in my workspace ! But in XIndice it is the same
| implementation, right ?
|
I don't know which implementation Xindice uses but I think you should be
able to use the release from xmldb.org by supplying it with a DOM from
Xindice and setting the system property
"org.infozone.tools.xml.queries.XPathQueryFactory" to whatever is your
XPathQueryFactory like this:
System.setProperty
("org.infozone.tools.xml.queries.XPathQueryFactory",
"org.infozone.tools.xml.queries.xalan2.XPathQueryFactoryImpl");
I tried your use-case and got this result:
Starting updates...
Updates done in 670 ms ...
result:
<?xml version="1.0" encoding="UTF-8"?>
<root KEY_id="0" maxid="1">
<statsnode KEY_id="1">
<loginfo KEY_key="Name">VDF import</loginfo>
<loginfo KEY_key="StartTime">2002/08/05</loginfo>
<loginfo KEY_key="FormatTime">Milli-seconds(528) Seconds(36)
Minutes(12) Hours(0)</loginfo>
<loginfo KEY_key="TransformationTime">MS[240] SE[0] MI[0]
HO[0]</loginfo>
<loginfo KEY_key="Status">Subscription success</loginfo>
</statsnode>
</root>
Seems like this result is what you're looking for. This was made with
Lexus' latest sources from xmldb.org. There was a bug in Lexus involving
cutting String in pieces when entity references were used and that is
solved now. Since your use-case doesn't use entity references (right?) I
don't know what the bug is in your release.
We will be releasing a new version of Lexus soon.
regards,
Jeroen Breedveld
--
X-Hive Corporation
e-mail: [EMAIL PROTECTED]
phone: +31 10 7108622
http://www.x-hive.com
----------------------------------------------------------------------
Post a message: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Contact administrator: mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
----------------------------------------------------------------------
