Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Namespace Not Being Inherited

From: Al Hatch <Hatch@---------------------.--->
To: NULL
Date: 7/1/2006 2:31:00 PM

An element node is supposed to inherit the namespace of its parent. But one 
of mine is not inheriting.

If I declare

<xsl:stylesheet 
xmlns:cm="urn:schemas-Professional-Plug-in:P2:ClipMetadata:v3.0">

then I should be able to prefix any node reference with "cm:" For example,

<xsl:value-of select="cm:P2Main/cm:ClipName" />

And, indeed, that does work in every parser I've tested, except... the Xalan 
parser used by FileMaker is complaining 

"XML parsing error: Attribute Œxmlns:cm¹ is not declared for element 
ŒFMPXMLRESULT².

But it is declared--in the very first line of the XSLT document!

 The complaining element lives in this template

<xsl:template match="/cm:P2Main/cm:ClipContent">
		<FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult">
			<ERRORCODE>0</ERRORCODE>
			<PRODUCT BUILD="07/1/2006" NAME="FileMaker Pro" VERSION="8.0v1" />
		
	<RESULTSET>
				<xsl:attribute name="FOUND">
					<xsl:value-of select="14" />
				</xsl:attribute>
				<xsl:call-template name="records" />
</RESULTSET>

	</FMPXMLRESULT>

I have tried to insert that xmlns:cm declaration everywhere in the document, 
but FileMaker still keeps complaining that it is an undeclared attribute.

Any ideas?



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent