More information on this bug:
- It only occurs with BPEL processes that were generated from a WSDL.
- The partner role defines the name space of the port type inside the partner link type definition. And not in the root mark-up.
I guess the designer removes the import because it does not seem to be used.
<ns4:partnerLinkType name="TuxDroidPortTypePLT">
<ns4:role xmlns:ns17="http://tuxdroid.ebmwebsourcing.com/" name="TuxDroidPortTypeRole" portType="ns17:TuxDroidPortType" />
</ns4:partnerLinkType>
<w:import location="tuxDroid.wsdl" namespace="http://tuxdroid.ebmwebsourcing.com/" />
It seems to only reject the import of the WSDL that describes the process.