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.
RFE to address the following usability issue. I wish to configure the WSIT options for a client port. In order to do so (in order for the tooling to permit me to access the WS Policy Attachment GUI at all), I must associate the port to a service WSDL binding for which WS Policies have been defined. To do this, I must: 1. Select the port in the CASA editor 2. Go to the Navigator window, access the properties of the port's port node. 3. Change the associated Binding to the right one. However, I cannot complete the final step, because in its current state, the editor(s) has no knowledge of the service WSDL bindings. So, prior to the above first step, I must: 1. Import the service WSDL into the CompApp project. 2. Use the WSDL editor to edit the CASA-generated WSDL file, and add an import of the file from the previous step. Note that the service WSDL has already been imported by the JBI module. In the case of a BPEL client project, it is imported so that it may be used in the BPEL process as the target of its service invocation. Instead of requiring users to import and reference the service WSDL a second time during Compapp configuration, usability would be improved if the CASA editor obtains the information from its JBI module(s), generate the necessary artifacts automatically, and eliminate these prepatory steps.
Created attachment 57589 [details] Service assembly with a callbackhandler class packaged in the sun-http-binding.jar service unit
Please disregard previous attachment, wrong ticket.