Re: [xsl] Detecting XML elements not transformed

[Michael Müller-Hillebrand <mmh@xxxxxxxxxxxxx>]

I usually put an xsl:message in the identity transform template to
tell me the otherwise unmatched element's and it's parent's names,
which of course requires that all supported elements have a matching
template.

Which XML structure should a separate XML with the unsupported
elements have, since they might be distributed all over the source
document, I guess?

- Michael M|ller-Hillebrand

Am 22.04.2008 um 09:06 schrieb Harry Liljestrvm:

> Hi All,
>
> I'm using Xalan-C version 1.10 and I have an input XML to be
> transformed to output XML.
>
> In other words, I have an application with XML configuration 3.x,
> which I upgrade to 4.x by using a XSL (v1.0) transform. All 3.x XML
> configuration elements are not supported in 4.x configuration. So,
> I would like somehow inform the user about those 3.x XML
> configuration elements which were not transformed during XSL
> transformation. The 3.x XML configuration is varying quite lot for
> different customers, so I would like to have a generally applicable
> way of detecting those 3.x XML configuration elements which were
> not transformed during upgrade. Is it possible to write a XSL
> template for this purpose?
>
> Could I e.g. somehow have two output files, conf4x.xml and
> notsupported.xml? conf4x.xml would contain the upgraded 4.x XML and
> notsupported.xml would contain those 3.x XML elements which were
> not tranformed.
>
> Does anybody have any ideas or examples of this?
>
> Thanks in advance,
>
> Harry

--
_______________________________________________________________
Michael M|ller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lvsungen und Training, FrameScript, XML/XSL, Unicode
<http://cap-studio.de/> -- Tel. +49 (9131) 28747