[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Detecting XML elements not transformed

Subject: Re: Detecting XML elements not transformed
From: Harry Liljeström <harry.liljestrom@xxxxxxxxxxxxx>
Date: Tue, 22 Apr 2008 12:45:30 +0300 (EEST)
Re:  Detecting XML elements not transformed
Thanks Michael for responding my question so quickly.

The unsupported.xml could have following XML structure:

   <node name="name_of_unsupported_node" xpath="xpath_to_unsupported_node"/>

The main idea here is, that when the application reads the upgraded 4.x
configuration and it shows an information dialog were it displays those
unsupported 3.x XML elements.

Does the xsl:message flush the message to std output? I don't need that, only
those output files (conf4x.xml and notsupported.xml) mentioned before.

By the way, what do you mean with "identity transform template"?



Michael M|ller-Hillebrand <mmh@xxxxxxxxxxxxx> kirjoitti:
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

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

Harry Liljestrvm

Mobile 358 400 985002

Email    harry.liljestrom@xxxxxxxxxxxxx

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.