Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342794 - Use XML catalog to resolve xsl include/import reference
Summary: Use XML catalog to resolve xsl include/import reference
Status: NEW
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xsl (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major with 1 vote (vote)
Target Milestone: Future   Edit
Assignee: David Carver CLA
QA Contact: David Carver CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-14 03:23 EDT by Matteo TURRA CLA
Modified: 2011-04-25 16:54 EDT (History)
1 user (show)

See Also:

Attachments
Test case project (4.00 KB, application/octet-stream)
2011-04-15 04:04 EDT, Matteo TURRA CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matteo TURRA CLA 2011-04-14 03:23:59 EDT 
Build Identifier: I20110310-1119

I would like to use the Xml Catalog feature to resolve xsl include/import reference (see: -URIRESOLVER option of xalan).
In the preference window "XML Catalog" it is possible to enter a catalog entry of type URI on for taglib definitions, DTD files and XSD files.
I added manually a catalog with a URI key referencing a xsl file (I did importing a manually modified catalog), but the catalog resolution doesn't work for include and import on xsl files.

Reproducible: Always

Steps to Reproduce:
1. Create a file with this content:
<?xml version="1.0"?>
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
	<uri name="http://www.mysite.com/library/constants.xsl" uri="library/constants.xsl"/>
</catalog>
2. import the file as catalog
3. create a new xsl file with this import element
	<xsl:import href="http://www.mysite.com/library/constants.xsl"/>
4. try to reference a template or a variable of the library/constants.xsl file
Comment 1 David Carver CLA 2011-04-14 15:54:10 EDT 
If you add the XML Commons resolver to your runtime transformation, then it will resolve the includes during transformation.

The XSL editor already supports the built in XML Catalog resolver for WTP.  You just need to import your Catalog into the WTP Catalog, and then the editor should resolve your import and includes.

If it doesn't then we have a bug.
Comment 2 Matteo TURRA CLA 2011-04-15 04:04:56 EDT 
Created attachment 193330 [details]
Test case project