Subject: RE: [xsl] Carrying Namespaces through a XSL to XSL Transformation From: "Julian F. Reschke" <julian.reschke@xxxxxx> Date: Fri, 29 Dec 2000 00:31:35 +0100 |
> 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: [xsl] 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Carrying Namespaces through a, Smith, Chad | Thread | Re: [xsl] Carrying Namespaces throu, Kevin McCarthy |
Re: [xsl] Page-break/Static content, Paul Grosso | Date | RE: [xsl] Carrying Namespaces throu, Julian F. Reschke |
Month |