This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The editor initially displays a service composition consisting of ports defined by the imported JBI module (e.g., BPEL module). When these ports are deleted (i.e., they are replaced by local ones created using the editor's palette), these ports are restored when the Composite Application is rebuilt. This is a problem when the old port and the new one use the same concrete properties that prevent deployment when their values colllide (e.g., HTTP URI services bind to). Sample projects to be attached shortly.
Created attachment 57318 [details] Client BPEL project
Created attachment 57319 [details] Service BPEL and Comp App projects
Instructions for attached sample: 1. Unpack, build and deploy the service (service.zip). This is a WS Security-enabled service implemented as a BPEL process. 2. Unpack the client BPEL project and open it in NetBeans. 3. Build the BPEL project. 4. Create a Composite Application for it. 5. Build the Composite App 6. Edit the Service Composition. 7. Create a new port, casaPort1. 8. Delete the "securedEchoPort" port. 9. Connect the BPEL JBI Module's consume endpoint to the provisioning endpoint of the new port, casaPort1. 10. Save changes, build the project. 11. The editor will refresh (but you may not see changes after the refresh). 12. Close the .casa file. 13. Edit the Service Composition again. 14. "securedEchoPort" is back again. For certain scenarios, such as WSIT scenarios using HTTP BC, this issue prevents runtime deployment of the WSIT client completely. The whole point of editing the service composition is because we cannot assign WSIT configuration to the original port. We have to replace it with a locally created one, and then assign WSIT attributes to the copy. The copy's definition is a facade to the original port, and must match its SOAP address. Since the original port is being un-deleted, we will have two ports attempting to bind to the same URI, and thus the deployment fails.
"Sierra" NetBeans DEV build 20080225050543 is what was used in reporting this problem.
Fixed, Changeset 70498:645f2f8099f1
Assigned to Sunil B for verification
Assigned to Sunil B for verification.
Closing the issue as the deleted port won't appear after the rebuild.