Subject:using oasis catalog in pipeline Author:Steve Cuzner Date:14 Oct 2008 09:39 AM
I'm building a pipeline application that does some xquery and then some xslt. My documents are valid xml and include a <!DOCTYPE statement at the top with a public identifier. I've added a user-defined catalog to my project, and I can run the xslt just fine. However, when I run the larger pipeline, it runs a choose node that applies an XQuery to determine the correct path to go down.
This is where I have my problem. The XQuery it throwing an error because it doesn't seem to know about the catalog. Is this a limitation of XQuery, Saxon, or is there a problem in executing a pipeline with a catalog?
Subject:using oasis catalog in pipeline Author:(Deleted User) Date:21 Oct 2008 09:27 AM
Hi Steve,
the only XQuery processor capable of processing an OASIS catalog is the Built-in processor; have you tried selecting it as the default XQuery processor for the pipeline?
Subject:using oasis catalog in pipeline Author:Steve Cuzner Date:21 Oct 2008 07:46 PM
If I do that, it certainly runs from the UI. But if I try to deploy as Java it fails saying that xslt isn't supported by that deployment scenario. If I change to Saxon, my xslt fails because it can't find the DTD specified in my catalog. I'm sure this can be done somehow, but I can't find documentation on how to do this.
Subject:using oasis catalog in pipeline Author:(Deleted User) Date:23 Oct 2008 12:34 PM
Hi Steve,
once you deploy a pipeline you can rely only on the services provided by the processor. So, unless Saxon can be instructed to use an OASIS catalog, you must make sure that the DTD references actually point to a valid location.
Subject:using oasis catalog in pipeline Author:Steve Cuzner Date:23 Oct 2008 12:44 PM
That is easy enough to do for saxon given Norm Walsh's entity resolver that has been added to Apache and can be used for Saxon and others. I guess I was expecting the use stylus studio URI resolver to do the trick or at least having the processor settings for Saxon allow for the specification of additional jars and properties files to the class path so that you can use the development IDE close to what will be deployed. Would you recommend an enhancement request?