Hi Igor,
I tried several times with my latest build of the BPEL editor, but I'm unable to reproduce the problem. The only differences in the artifacts.wsdl AFTER creating the new partnerlink was the addition of the new partnerlink definition, just before the <types> element (which is what I would expect):
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of services participating in this BPEL process
The default output of the BPEL designer uses strings as input and
output to the BPEL Process. But you can define or import any XML
Schema type and us them as part of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="calcPLT">
<plnk:role name="calcClientRole" portType="wsdl:RectangleCalculator"/>
</plnk:partnerLinkType>
<import location="RectangleCalculator.wsdl" namespace="http://rectangle.bple.tps"/>
<types>
<schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://eclipse.org/bpel/sample"
xmlns="http://www.w3.org/2001/XMLSchema"
>
The section in bold is what was added to the WSDL. It is possible that this problem has been fixed as part of another bug. If you have time, can you please try a more recent build of the JBoss tools (use a nightly build) and see if you still get the error?
Also, if you could post the XSD and WSDL that you are using to this forum, that would help.
Thanks!
Bob