RE: Carrying Namespaces through a XSL to XSL Transform
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Smith, Chad > Sent: Wednesday, December 27, 2000 7:13 PM > To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx' > Subject: Carrying Namespaces through a XSL to XSL Transformation > > > > Because of the inability to convert XPath strings to XPath > nodesets, I am > > forced to perform XSL to XSL Transformations. these > transformations have > > worked out well with a single exception: I cannot migrate more than one > > namespace to the resulting XSLT file. This is a problem because I would > > like for the resulting XSLT to utilize some form of embedded script, but > > since I am using Xalan, this requires two additional namespaces. > > > > I am currently using 'xsl:namespace-alias' to carry over the actual XSL > > namespace, however multiple uses of this tag with different > properties do > > not migrate additional namespaces but only attempt to overwrite > the first. > > > > Any ideas? Maybe this is a stupid question -- but why would you need to do anything specific to "carry over" the namespace declarations? I see why you need xsl:namespace-alias for the actual XSLT code generated (done that myself a lot of times), but for the rest? AFAIK, XSLT will keep all namespaces declared in your source document unless you use exclude-result-prefixes to avoid that... XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format