Altova Mailing List Archives

RE: [xsl] no attributes outputed when chaining transformations

From: "Andrew Welch" <ajwelch@--------------->
Date: 12/16/2004 11:57:00 AM
> Hello,
> maybe someone can shed some light on this one:
> If I follow the xalan Pipe or UseXMLFilters samples and chain
> together
> my transformations I do not get the same result as when I
> perform these
> transformations separately, i.e. If I do A -> B and then B->C  in two
> separate steps then I get my desired result. However If I do
> A->B->C by
> chaining I do not get the same result as above.
> Specifically when I use chaining I do not see any attributes, in any
> element that should have attributes. Other than that the results are
> identical.
> Can anyone think why this may happen? I can also post my
> input xml and
> xsl files if that would help.

Not much to go on here, but it could be that if you generating SAX
events from the result of A->B for the input of transformation C, you
are creating a new AttributesImpl() object instead of using the existing
object (typically 'atts') in the startElement() call.  It would be less
wild speculaton if you posted the method that chains the transforms :)



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.