Practical Usage


Practically speaking, Xindice works best on JDK 1.3. You should definitely run the Xindice server under JDK 1.3. On the client side, you can use JDK 1.4 for most of the XML:DB Core Level 0 and Level 1 APIs. If you see odd unexplainable errors, you can try running your client application under JDK 1.3 to see if that solves the problem. If you need to run your client application on JDK 1.4, then you’ll need to use the Java Endorsed Standards mechanism to override the JDK 1.4 built-in XML and XSL processors with the versions of Xerces and Xalan distributed with Xindice. Applications that use XUpdate will be affected by the versions of Xerces and Xalan that are available. The easiest way to deal with the Endorsed Standards Mechanism is to make your own copies of the Xindice batch or shell script file and edit it to do the override for you. You should also create a script that sets up the override for your own applications (see http://home1.gte.net/greno/Updated_Batch_Files_for_Xindice_1_0.htm).

When you create resources in an Xindice collection, it’s better to supply the names for the resources. It’s true that Xindice generates IDs for you; but often during development you’ll want refer to specific resources, and it’s easier to do this if you control the system used to name them.

You need to keep in mind that Xindice is a database system. One of the keys to good performance in database systems is building the right indices. When you create a collection, you should think carefully about the kinds of queries you’re going to make on that collection and create indices that will help the common cases.




Professional XML Development with Apache Tools. Xerces, Xalan, FOP, Cocoon, Axis, Xindice
Professional XML Development with Apache Tools: Xerces, Xalan, FOP, Cocoon, Axis, Xindice (Wrox Professional Guides)
ISBN: 0764543555
EAN: 2147483647
Year: 2003
Pages: 95

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net