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.
NetBeans is an excellent platform for developing WebServices but it is let down by its WDL editor. I think maybe the GUI came to be in RPC times. The support for Doclit is not very helpful and for doclit wrapped non existant. I hate to mention the E word but the WSDL editor in Eclipse is far more productive and efficient. Take adding an operation (doclit) for example. In Eclipse it is one click: the operation is added, including the corresponding messages and types with the correct names. In NetBeans you add the operation, then the messages, then connect the messages to the operation, then the schema types for the messages and then connect the messages to the types. I am often primarily occupied with defining interfaces via wsdl as contracts for our WS developers. I can produce a WSDL in Eclipse in a fifth of the time it takes in NetBeans (yes I have timed it). I'm not asking for a complete redesign of NetBeans, only a wizard / dialog to aid the adding of doclit and doclit wrapped operations.
Thanks for taking the time to provide feedback. Do you think an option to create automatic wrapper elements for the part types in the abstract configuration panel will be useful? The problem that I see is that you need to create the schema in advance before you can select the doc literal binding. If the wizard/dialogs provided a way to create wrapper for the part types automatically, this should fix the problem. let me know if the evaluation is correct. or you were pointing to something else. Also let me know if there are any other issues, that you would like to be added/fixed.
Many thanks for the reply. What I was thinking of was taking it a step further. When you add a new operation the messages, parts, schema types and the connections between the types are automatically created. That is the commonest use case anyway (AFAIK). Look at the various possiblities: 1. New operation with existing messages 2. New operation with new messages with existing types 3. New operation with new messages with new types 1 is not doclit as far as I know. 2 is not doclit wrapped. The only question that remains is whether the user wants to use a complex type or an element for the parameters. That could be controlled using a radio button.