Bug 95346

In latest build (2007/02/12) BPEL Editor/Mapper is qualifying element inside
XPATH expression for Assign, when it should not. This was working 2007/02/08 build.

Local or Non global elements should not be qualified when Schema has
elementFormDefault="unqualified" or when attriibute elementFormDefault is not
present.

Note there is a bug which asks for qualification for global elements.
http://www.netbeans.org/issues/show_bug.cgi?id=93704

Steps to reproduce.
1. Create a BPEL project.
2. Copy attached WSDLs to "Prcoess Files" folder.
3. Creat new Business Process file.
4. Drag and Drop processApplicant.wsdl in to the BPEL editor. Select
"processApplicantPortTypeRole" as myRole.
5. Drag and drop NameParserWsWrapper.wsdl in to the BPEL editor. Select
"NameParserWsRole" as partner Role.
6. Add following activities in sequence, "Recieve", "Assign", "Invoke", "Assign"
and "Reply".
7. LInk Recieve and Reply to PartnerLink1/processApplicantPortTypeRole and
create instance and variables as required.
8. Link Invoke  to PartnerLink2/NameParserWsRole variables as required.
9. Click on Assign1, in the mapper, link ProcessApplicantOperationIn.part1 to
getFirstNameIn.parameters.fullName.
10. Save and switch to Source view.
11. Code generated for Assign is,
        <bpws:assign name="Assign1">
            <bpws:copy>
                <bpws:from variable="ProcessApplicantOperationIn" part="part1"/>
                <bpws:to>$GetFirstNameIn.parameters/ns3:fullName</bpws:to>
            </bpws:copy>
        </bpws:assign>

Note prefix ns3 for element "fullName".

12. In XSD, Element "fullName" is defined as below.
<xs:complexType name="getFirstName"><xs:sequence><xs:element name="fullName"
type="xs:string" minOccurs="0"></xs:element></xs:sequence></xs:complexType>

13. Schema does not contain attribute "elementFormDefault", so default is
"unqualified".