|
Subject: [xsl] Design Question: XSLT Configurable From: Matthias Müller <pymote@xxxxxxxx> Date: Tue, 21 Jul 2009 08:33:27 +0000 (GMT) |
Hi there,
i work on a application that let the users configure it to their
needs using a certain file (a user-settings.xml)
during the years this file
has changed, so there exist different versions now. my idea is to transform
all of them to the newest version.
the configuration file is a very simple xml
file (max 2 levels), the changes are also moderate (create node, delete node,
rename node and merge content of nodes).
the thing is, i want to keep the
transformation expandable by only configuring what have changed from version
to version.
e.g. like that
-------------------------------------
<Versions>
<Version nr="0.3">
<Actions>
<RenameAction
fromElement="elementA" toElement="elementD"/>
</Actions>
</Version>
<Version nr="0.2">
<Actions>
<MergeContentAction toElement="elementA" separator=" ">
<MergeFromElement name="elementB"/>
<MergeFromElement
name="elementC"/>
</MergeContentAction>
</Actions>
</Version>
<Version nr="0.1">
</Versions>
-------------------------------------
so, i only will have one transformation
file instead of a file for each version.
what about this approach? i think
that this is supposed to be a common issue, isn't it?
Thanks for your ideas,
Matthias
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] counter vs. functional co, Jeff Shelley | Thread | RE: [xsl] Design Question: XSLT Con, Michael Kay |
| Re: [xsl] counter vs. functional co, Andrew Welch | Date | RE: [xsl] Design Question: XSLT Con, Michael Kay |
| Month |