Steps to reproduce:
- create a new Sync sample
- create new Web Application, add a Web Service there
- deploy web service
- drag Web Service node to the BPEL process
- PartnerLink editor will appear. Accept defaults
- drag Web Service once more, press Cancel when the PartnerLink editor opens
The PartnerLink created after first drag-N-drop will be marked invalid:
PartnerLinkType definition will be deleted from WSDL
*** This issue has been marked as a duplicate of 84622 ***
Verified in build 2006.09.27
I don't think this is a duplicate of bug 84622.
In that bug, the cancel is failing to delete the retrieved files, which was what
bug filer thinks should be done if there is no pre-existing PartnerLink.
In this case, the PartnerLink already exists, so the DnD should actually try to
allow user a chance to quit earlier - like "PartnerLink already exists for this
WSDL are you sure you want to overwrite. Y/N?" If this could be done before the
retrieval is invoked it would be best. This is tricky, since for EJB/WS we don't
have the WSDL yet. So check would have to be done against WS name if possible.
Anyway, this seems like a different use case and we should not lose track of it,
so I think it is worth keeping open and distinct from other use case.
It is a UI issue - reassigning to Alexey
Same as 84622
Changed target milestone from Sierra to 6.1 in order to display correct info on
NB 6.1 dashboard
Tested and closed with NetBeans IDE 6.5.1 (Build 200904031800).
QA believes this is not a duplicate of 84622, but this is not an issue at with this current build. Trying to drag an
existing Web Service onto the Design View results in a validation message stating "A name for the new Partner Link Type
has to be unique." Although the user can modify the name and then accept the "duplicate" Web Service WSDL, this seems
to be a reasonable notification to the user.
A subsequent cancellation at the PartnerLink editor no longer deletes either of the existing WSDLs, and therefore fixes
the symptom described.