Opened 18 years ago
Closed 17 years ago
#1531 closed task (fixed)
Composing mulitiple XML files using 1 or more XSLTs
Reported by: | Owned by: | roadrunner | |
---|---|---|---|
Priority: | normal | Component: | XsltMacro |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
I must split apart one large XML file into several smaller parts. I need to combine some or all of these parts at times with one XSLT using your the macro.
Have you experimented with this. The xsltproc performs the correct transformation on my XML/XSLT files in a directory, but I get nothing when using the same files in trac pulled from a repository. No errors and no output.
HTML headers are excluded from the output.
Any ideas?
Thanks,
Jason Carter
Attachments (1)
Change History (4)
Changed 18 years ago by
Attachment: | AllProducts.xsl added |
---|
comment:1 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 17 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
The problem was that if the docs were pulled from something other than a direct file then parsing was on a stream with no url associated with it, and hence there was no way for the parser/transformer to resolve relative urls. Additionally the transformer doesn't know how to load urls with arbitrary schemes. So, we now make sure a url is always associated with each source being parsed and we register an entity-loader that knows how to resolve our internal urls that represent things like repository entries or attachments.
comment:3 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
(In [2312]) Fix #1531. Added an entity-loader to handle relative links inside the stylesheet and/or xml-doc. As part of this did some refactoring and created a TransformSource class and appropriate subclasses to encapsulate and simplify all the code related to the differing sources.