[oXygen-user] Catalog URI Resolver for XSLT Include/Import in Editor?

Sorin Ristache
Wed Jul 8 04:17:15 CDT 2009


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.


Eliot Kimber wrote:
> On 7/7/09 7:59 AM, "Eliot Kimber" <> 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.

More information about the oXygen-user mailing list