Geert Josten wrote:
Ah, I really ought to test things before I shout something...
Could you send us the result after the first step?
Here is the result after the first step:
<?xml version="1.0" encoding="UTF-8"?>
<testPlan xmlns="http://www.virtc.com/jdep/att";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.virtc.com/jdep/att
D:/jdep/ATTCON~1/ATT_1_0_8/TestPlan.xsd"
testPlanName="CRSAcceptanceSouthPole" baseDir="${TEST_BASE_DIR}"/>
notice the attributes are all present and our default namespace has now
correctly changed according to this transform.
Things might get mixed that are straightened out by serializing and
parsing again. A bit like why you have to serialize when using
disable-output-escaping to add XML structure or entities (not a good
practice anyhow!)...
It appears that could be what is happening. I agree this is not a good
practice especially since we have the facility to avoid repeated
serailizing and reparse. That's why I have been trying to see if I can
get chaining to work before resorting to a less optimal workaraound.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--