Netbeans version used: netbeans-trunk-nightly-200708061200-full.zip

This falls in the validation of the schema related paths, and also tied to the relative path support in the editor.

consider the following xsl construct 

    <xsl:template match="/">
        <xsl:element name="ns:CustomerHistoryEntries">
            <xsl:for-each select="ns1:Orders/ns1:Order">
                <xsl:element name="ns:CustomerHistoryEntry">
			    <xsl:element name="ns:OrderLookupInfo">
                        <xsl:for-each select="ns1:OrderItems/ns1:item">
                            <xsl:element name="ns:ITM_NUMBER">
                                <xsl:value-of select="ns1:ITM_NUMBER"/>
                            </xsl:element>
                        </xsl:for-each>
                    </xsl:element>
                </xsl:element>
            </xsl:for-each>
        </xsl:element>
    </xsl:template>

if i change the xpath expression in the line below as shown

<xsl:for-each select="ns1:Orders/ns1:Ordeeeeeeeeeeeeeeer">

the xslt editor should inform the user that the xpath expression is invalid and ask for correction.

currently it will allow the project to be build and at runtime the xsl processor ignores the xsl construct as it cannot
find the specified path (as it does not exist) as does not generate any input.

The user does not have any indication why his transformation failed