problem

useability tests have shown that users are not aware that wsdl files must have
PLT (partner link type) defintions BEFORE it can be used in a BPEL file to
create a a PL (partner link). Therefore, users typically drag WSDL w/out partner
link onto diagram. Today, diagram detects taht there is not PLT and assumes user
only wants to add wsdl as import. And import editor appears. 

This is bad because we are making wrong assumption. User probably wants to
create partner link and probably does not know they need a PLT first. 

It is also bad because there are two differnt editors that user might see when
DnD of wsdl. They might see PLT editor or they might see import editor. This was
my fault for design. We need to reworks so that user only sees one editor no
matter whether wsdl has PLT or not.

However, there are SOME cases where user may want to add WSDL exclusively as
import, so we also need to consider that possibillity in revised solution. See
discussion of "import only" option below.

Recommended solution.
Rework the PL editor to allow for:

1) Give user choice of creating new PL from existing PL or new PL

2) creation of new PLT (this means forward engineering the new PLT into the WSDL
artifact).


Import only option ? (otional) - we may want to give user choice of "only add
import - do not add PL" (this is for small use case where user is importing wsdl
for purpose of using embedded schema but does not need partner. It is debateable
whether this is a valid use case. Technically, it could happen, but it would
seem to be a very strange case. Perhaps we should not complicate PL wizard with
this use case. Perhaps it is sufficient to have this strange use case covered by
the "Add Import action" on the Navigator Imports node. I vote for keeping this
complexity out of the PL wizard.