Please refer to bug http://enterprise.netbeans.org/issues/show_bug.cgi?id=93704.

This bug for validation the xpath expression such that it takes 
elementFormDefault into account to make sure xpath expression generated is a 
valid one.


Consider the schema 
<xsd:schema targetNamespace="http://xml.netbeans.org/schema/RefElemSchema"
xmlns:tns1="http://xml.netbeans.org/schema/RefElemSchema">
            <xsd:element name="intElem" type="xsd:int"></xsd:element>
            <xsd:element name="strElem" type="xsd:string"></xsd:element>
            <xsd:complexType name="MsgType">
                <xsd:sequence>
                    <xsd:element ref="tns1:intElem"/>
                    <xsd:element ref="tns1:strElem"/>
                </xsd:sequence>
            </xsd:complexType>
            <xsd:element name="MsgElem" type="tns1:MsgType"></xsd:element>
</xsd:schema>
Here the complextype 'MsgType' has Element Reference to the global elements
'intElem' and 'strElem'. Even though the <schema> tag does not define the
attribute 'elementformdefault=qualified', the element references to the global
elements have to be qualified when being used in the bpel assignments.

The assignments that are generated for assign between variables defined on
messages based on the schema above are shown below

        <bpws:assign name="Assign2">
            <bpws:copy>
                <bpws:from>$IntPTOperOut.part1/intElem</bpws:from>
                <bpws:to>$ExtPTOperOut.part1/intElem</bpws:to>
            </bpws:copy>
            <bpws:copy>
                <bpws:from>$IntPTOperOut.part1/strElem</bpws:from>
                <bpws:to>$ExtPTOperOut.part1/strElem</bpws:to>
            </bpws:copy>
        </bpws:assign>

intElem and strElem are not qualified and have to be qualified. 

The validation should validate and report error saying that inElem in 
$IntPTOperOut.part1/intElem should be namespace qualified with a prefix.
similarly strElem in $IntPTOperOut.part1/strElem should be namespace qualified 
with a prefix.