Replacing the namespace

madowl · February 29th, 2012, 05:30 PM

Good day all,
I have the following xml name space that I want to replace:
<CommonRecord xmlns="http://www.ed.gov/FSA/COD/2010/v3.0d" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ed.gov/FSA/COD/2010/v3.0d CommonRecord3.0d.xsd">

Below is my xslt transforming code. However, I do not see this as being replaced.
<xsl:stylesheet version="2.0"
xmlns:v="http://vocado.vsm-systems.com/xsd/vocado-tx"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:default="http://www.ed.gov/FSA/COD/2011/v3.0e" exclude-result-prefixes="default">

<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>



<xsl:variable name="latestUsdeNameSpace" select='"http://www.ed.gov/FSA/COD/2011/v3.0e"'/>


<xsl:template match="//default:*">
<xsl:element name="{local-name()}" namespace="{$latestUsdeNameSpace}">
<xsl:apply-templates select="@* | node()"/>
</xsl:element>
</xsl:template>


<xsl:template match="@* | node()">
<xsl:copy copy-namespaces="no">
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>

samjudson · February 29th, 2012, 05:52 PM

You have the default namespace declared as the new namespace, but are wanting to match the old one.

xmlns:default="http://www.ed.gov/FSA/COD/2011/v3.0e"

should be

xmlns:default="http://www.ed.gov/FSA/COD/2010/v3.0d"

Also, there is no need for the "//" in front of your match statement.

madowl · February 29th, 2012, 05:57 PM

Thank you for that Sam. However, the default could be anything. Regardless of what it is, I want all xml files running through this xslt to inherit http://www.ed.gov/FSA/COD/2011/v3.0e. How do I achieve this?

mhkay · February 29th, 2012, 06:32 PM

Then just replace the pattern in the template that matches default:* with match="*", and get rid of the existing match="*" template.

madowl · February 29th, 2012, 06:55 PM

Thank you Mr.Kay. I am a bit new at this so please bear with me. That did only a partial replace though. I am left with
<CommonRecord xmlns="http://www.ed.gov/FSA/COD/2011/v3.0e">http://www.ed.gov/FSA/COD/2010/v3.0d CommonRecord3.0d.xsd

My changes are as folows:
<xsl:stylesheet version="2.0"
xmlns:v="http://vocado.vsm-systems.com/xsd/vocado-tx"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:default="http://www.ed.gov/FSA/COD/2011/v3.0d">

<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>



<xsl:variable name="latestUsdeNameSpace" select='"http://www.ed.gov/FSA/COD/2011/v3.0e"'/>


<xsl:template match="*">
<xsl:element name="{local-name()}" namespace="{$latestUsdeNameSpace}">
<xsl:apply-templates select="@* | node()"/>
</xsl:element>
</xsl:template>




</xsl:stylesheet>

mhkay · March 1st, 2012, 04:54 AM

Your template is doing apply-templates to process attribute nodes but you no longer have a template rule that handles attribute nodes. Replace the

Code:

<xsl:apply-templates select="@*|node()"/>

with

Code:

<xsl:copy-of select="@*"/>
<xsl:apply-templates/>

madowl · March 6th, 2012, 12:07 AM

Hi Michael,
I am running into this error upon transformation. There are certain elements like this:
<EmailAddress xsi:nil="true"></EmailAddress>
When such elements are encountered the xslt is throwing the error:
Undeclared namespace prefix in DOM input: xsi
I want to keep these elements but disregard the xsi:nil="true". In other words this should be <EmailAddress /> or <EmailAddress> </EmailAddress>
WHat would you recommend in this case? My code is as follows:

Code:

<xsl:stylesheet version="2.0"
                xmlns:v="http://vocado.vsm-systems.com/xsd/vocado-tx"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:default="http://www.ed.gov/FSA/COD/2011/v3.0e" exclude-result-prefixes="default">

    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>

    <!--Define the latest name space-->

    <xsl:variable name="ns" select='"http://www.ed.gov/FSA/COD/2011/v3.0e"'/>
    <!-- This template will plug the latest name space in -->
    <xsl:template match="*">
        <xsl:element name="{local-name()}" namespace="{$ns}">
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates/>
        </xsl:element>
    </xsl:template>
</xsl:stylesheet>

mhkay · March 6th, 2012, 04:58 AM

One of the unfortunate things about DOM (one of many...) is that it allows you to construct trees that do not represent well-formed XML documents. XSLT will only handle input that is well-formed (and namespace-well-formed). If you give it a DOM that contains namespace prefixes with no corresponding declarations, it will choke.

You probably won't like my recommendation but I will give it anyway: stop using DOM. Ideally, do all your XML manipulation in high level languages - XSLT and XQuery. If you can't achieve that and need to use Java, then use one of the more modern tree representations such as JDOM or XOM.

madowl · March 6th, 2012, 10:40 AM

Hi Michael, I see what you are saying and it makes sense from a technical standpoint. However, DOM is used throughout the application and hence am kind of stuck using it