Catalog URI Resolver for XSLT Include/Import in Editor?
I'm finding myself in the situation where I want to edit style sheets that will, ultimately, use custom URIs to point to resources. For editing on the file system it would be easiest if I could use an XML catalog to map my private URIs to the files on my file system so the same reference will work as developed and as deployed. Is that possible today? I didn't see anything likely in the help or searching on URI resolver in the mailing list archives. Thanks, Eliot ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
Hello, Oxygen creates a URI resolver from the XML catalogs added in Preferences -> XML -> XML Catalog and sets the resolver to the processors Saxon, Xalan, xsltproc. OASIS 1.1 catalogs are supported. The URIs used in xsl:include and xsl:import are resolved with uri entries of the catalogs. You can find in the User Manual that XML catalogs are used for mapping the system ID, the public ID or the URI of a resource: http://www.oxygenxml.com/doc/ug-oxygen/using-XML-Catalogs.html http://www.oxygenxml.com/doc/ug-oxygen/preferences-xml.html#preferences-xml-... Regards, Sorin Eliot Kimber wrote:
I'm finding myself in the situation where I want to edit style sheets that will, ultimately, use custom URIs to point to resources. For editing on the file system it would be easiest if I could use an XML catalog to map my private URIs to the files on my file system so the same reference will work as developed and as deployed.
Is that possible today? I didn't see anything likely in the help or searching on URI resolver in the mailing list archives.
Thanks,
Eliot
On 7/7/09 2:52 AM, "Sorin Ristache" <sorin@oxygenxml.com> wrote:
Hello,
Oxygen creates a URI resolver from the XML catalogs added in Preferences -> XML -> XML Catalog and sets the resolver to the processors Saxon, Xalan, xsltproc. OASIS 1.1 catalogs are supported. The URIs used in xsl:include and xsl:import are resolved with uri entries of the catalogs.
Cool--that worked. I didn't get from the referenced help pages that this would apply to xsl:import and xsl:include. It just says "or a URI reference (at document transformation)"--would be clearer if it explicitly says something like "for xsl:import and xsl:include" or lists all the cases where it applies (for example, does it also work for document() function calls to? Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
On 7/7/09 7:59 AM, "Eliot Kimber" <ekimber@reallysi.com> wrote:
On 7/7/09 2:52 AM, "Sorin Ristache" <sorin@oxygenxml.com> wrote:
Hello,
Oxygen creates a URI resolver from the XML catalogs added in Preferences -> XML -> XML Catalog and sets the resolver to the processors Saxon, Xalan, xsltproc. OASIS 1.1 catalogs are supported. The URIs used in xsl:include and xsl:import are resolved with uri entries of the catalogs.
Cool--that worked. I didn't get from the referenced help pages that this would apply to xsl:import and xsl:include. It just says "or a URI reference (at document transformation)"--would be clearer if it explicitly says something like "for xsl:import and xsl:include" or lists all the cases where it applies (for example, does it also work for document() function calls to?
OK, next level: is there a way to parameterize the uri= value to reflect Oxygen-defined variables? My goal in this case is to have a catalog used for development purposes where the uri= value points to developer-specific location (in this case, transform components provided by a separate project in CVS). Would like to have the catalog be invariant, with developers configuring it by locally setting a property. Is that possible in Oxygen today? For my environment, being able to use properties set in an Any property file would be ideal, since I'll have to configure the same property for use by Ant as well. Note that this is in the context of the standalone Oxygen editor, not the Eclipse plugin version. Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
Hello, The XML catalogs are used also for document() function calls. It is not possible to parameterize the uri= value with Oxygen editor variables. The catalog resolver does not know to resolve the values of the Oxygen editor variables. If we modify the resolver used in Oxygen for allowing editor variables the catalogs cannot be used in other applications. For example in Ant you have to replace the built-in catalog resolver with the modified resolver from Oxygen. Regards, Sorin Eliot Kimber wrote:
On 7/7/09 7:59 AM, "Eliot Kimber" <ekimber@reallysi.com> wrote:
it applies (for example, does it also work for document() function calls to?
OK, next level: is there a way to parameterize the uri= value to reflect Oxygen-defined variables?
My goal in this case is to have a catalog used for development purposes where the uri= value points to developer-specific location (in this case, transform components provided by a separate project in CVS). Would like to have the catalog be invariant, with developers configuring it by locally setting a property.
Is that possible in Oxygen today? For my environment, being able to use properties set in an Any property file would be ideal, since I'll have to configure the same property for use by Ant as well.
Note that this is in the context of the standalone Oxygen editor, not the Eclipse plugin version.
Cheers,
E.
participants (2)
-
Eliot Kimber -
Sorin Ristache