Collection of XSLT Editor issues encountered when designing PurchaseOrder to CustomerHistory Transform using XSL Templates

Netbeans version used: netbeans-trunk-nightly-200708061200-full.zip
Project file attached: PurchaseOrder.zip

Issues:
1. The editor mandates that the newly created .xsl file should always have a default template.

The 'orderToCustTransform.xsl' when created has a default root template defined.

	<xsl:template match="/">
	</xsl:template>

Since the editor does not yet support template creation, manually changing this to have default templates as shown

    <xsl:template match="ns:Orders">
        <CustomerHistoryEntries xmlns="http://xml.netbeans.org/schema/custhistory"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="http://xml.netbeans.org/schema/custhistory custhistory.xsd">
            <xsl:apply-templates/>
        </CustomerHistoryEntries>
    </xsl:template>

leads to error message in the design view 
"The XSLT file does not contain a root template element"

It is not mandatory that a .xsl file should contain a root template element.

2. Creation of another XSLT service updates the transformmap.xml file in a incorrect manner.

The original entry in the transformmap.xml corresponding to the 'orderToCustTransform.xsl' is as follows

    <service partnerLinkType="ns1:orderServicePLT" roleName="orderServicePortTypeRole">
        <operation opName="orderServiceOperation" inputVariable="inOpVar1" 		outputVariable="outOpVar1">
            <transform file="orderToCustTransform.xsl" source="inOpVar1.orderPart" 			   result="outOpVar1.custHistPart"/>
        </operation>
    </service>

Creating a duplicate service ex: 'TestXSL' in the same XSLT project, updates the transformmap.xml in the following manner.

    <service partnerLinkType="ns1:orderServicePLT" roleName="orderServicePortTypeRole">
        <operation opName="orderServiceOperation" inputVariable="inOpVar1" 	outputVariable="outOpVar1">
            <transform file="orderToCustTransform.xsl" source="inOpVar1.orderPart" 		   result="outOpVar1.custHistPart"/>
            <transform file="TestXSL.xsl" source="inOpVar1.orderPart" 		   result="outOpVar1.custHistPart"/>
        </operation>
    </service>

There should not be another <transform> element in the same operation but it should either be a new 
separate <service> element or under the same <service> element a separate <operation> element.