Using non-literals in literal element structure

Neal · March 17th, 2009, 07:36 AM

xml version="1.0"

Hi,

When saving the xslt file (below), it appeared easier to code using literal result elements rather than the xsl:element approach.

I found this was perhaps due to the inclusion of:
'xsi:noNamespaceSchemaLocation'
(http://first4farming.com/F4FXML/Schemas/v3_0_2/F4FInv.xsd)
My problem is that once the root element 'F4FInvoice' is selected, I can't call a further template or add a non-literal element without producing an error (i.e.

Mandatory Element is expected

or

Only text allowed inside [Element Name])

Code:

 
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msg="http://schemas.microsoft.com/dynamics/2006/02/documents/Message" xmlns:si="http://schemas.microsoft.com/dynamics/2006/02/documents/SalesInvoice" xmlns:xsi="http://first4farming.com/F4FXML/Schemas/v3_0_2/F4FInv.xsd" xmlns:js-function="//CALjs-functions">

<!-- Import the CAL js-functions template -->
<xsl:import href="CALjs-functions.xslt"/>
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" omit-xml-declaration="yes" />
<xsl:variable name="DteTmeNow" select="js-function:DateTimeNow()"/>
<xsl:variable name="strAction" select="./msg:Envelope/msg:Header/msg:Action"/>
<xsl:variable name="strDestEndPnt" select="./msg:Envelope/msg:Header/msg:DestinationEndpoint"/>
<xsl:variable name="strDocPurpose" select="./msg:Envelope/msg:Body/si:SalesInvoice/si:DocPurpose"/>

<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="/">
<xsl:choose>
<!--In the specification-->
<xsl:when test="$strDestEndPnt='F4F_S1_SendSalesInvoice' and $strAction='readSalesInvoice' and $strDocPurpose='Original">
<xsl:call-template name="F4FInv1"/>
</xsl:when>

<xsl:otherwise>
<xsl:call-template name="F4FInv7"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

<xsl:template name="F4FInv1">
<F4FInvoice xsi:noNamespaceSchemaLocation="http://first4farming.com/F4FXML/Schemas/v3_0_2/F4FInv.xsd" InvoiceType="Invoice" DocumentType="New" TypeOfSupply="Sale" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<F4FDocumentHeader>
<SchemaVersion>3</SchemaVersion>
<SchemaStatus>Approved</SchemaStatus>
<DocumentCreated DateTimeType="Document Created">
<!--<xsl:value-of select="js-function:DateTimeNow()"/>-->
<xsl:text>20090216 10:00</xsl:text>
</DocumentCreated>
</F4FDocumentHeader>
<xsl:call-template name="DocHdr"/>
<xsl:call-template name="InvHdr"/>
<xsl:call-template name="TrnsDtls"/>
<xsl:call-template name="InvLine"/>
<xsl:call-template name="TaxTrail"/>
<xsl:call-template name="InvCtrlTtls"/>
</F4FInvoice>
</xsl:template>
</xsl:stylesheet>

Is there a method to by-pass this, so I can execute the non-literals

<xsl:text>20090216 10:00</xsl:text>
or
<xsl:call-template name="DocHdr"/>

Thanks in advance,

mhkay · March 17th, 2009, 07:48 AM

You don't make it clear whether this error is occurring in your XML/XSLT editor or when you compile the stylesheet.

Anyway, some tools attach unreasonable significance to the presence of an xsi:schemaLocation attribute, and treat it as a license to perform schema validation, which you don't want to happen here. You could of course switch to generating this attribute using xsl:attribute, or if you prefer you could use <xsl:namespace-alias> to set an alias for the xsi namespace, so that the namespace used in the stylesheet is different from the "real" xsi namespace.