Hi Bill,
I've done quite some conversions, bi-directional also, and I tend to agree that it would be a lot
easier for you to place some kind of mapping in the center. If the logic can generate xslt, then it
should be fairly easy to generate a mapping as well. Though it would make more sense to me if the
logic would create a mapping first and some code generates an xslt out of it. One of the benefits is
that a mapping could be presented in a customer-readable form. That is quite difficult with an XSLT...
Grtz,
Geert
Hi
Workflow:
User runs logic to create xslt file, its serialized.
Some time later the User re-selects the xslt file to be
analyzed.
Need to use the xslt file as an input.
When you generate the stylesheet, could you also generate another file that
contains the mappings and then analyze that instead of the actual stylesheet?
If not, then annotate the stylesheet literal result elements (and xsl:element
generated element nodes) with an identifier, as suggested by David.
Cheers,
Jarno