WSDLEditor.Specification61

WSDL Editor Main Page

WSDL Editor Enhancements for 6.1

Contents

Go to Definitions

Go To Definitions should be added to Part, Input, Output, Fault, Binding and Port, so that user can navigate to the definitions easily. This would be provided in the Go To pop-up menu.


Enhance Drag N Drop in Partner view.

Generic Behavior

  • All palette item drops creates the new widget and makes it editable, so that user can change the name.
  • Widgets created by add buttons, also is editable.

Define the behavior of various drops in partner view:
Partnerlinktype :

  • Drop PartnerLinkType from palette and Add PartnerLinkType button
  • Both create a default role.

Message

  • Drop Message from palette and Add Message button (in messages section)
  • Creates a message with a part.
  • Default message name is "message{N}"; where N is a number starting from 1.
  • Drop message from palette on a Operationparameter (input/output/fault).
  • Default message name = {operationName}{Suffix}; where Suffix is Fault| [Request ] depending on whether its input, output or fault.
  • This creates a new message with a part and sets the OperationParameter's message to the newly created message.
  • Drop message from navigator on OperationParameter.
  • Sets the operationparameter's message to the dropped message.
  • Drag Message from Messages section in partner view to OperationParameter.
  • Ctrl enables drag on message widgets in messages section.
  • Drop on operationparameter sets the message to the dropped message.

Part :

  • Drop schema element or type node from navigator to on a message to create a new part.
  • Default part name = part{N}; where N starts from 1
  • Drop schema element or type node from navigator on a part to change the element or type to the dropped node.

Role

  • Drop port type node from navigator
  • Sets the role's port type to the dropped port type.

Optional PartnerLinkType automatic generation

A check box will be shown to the user in existing dialogs/wizards, which will provide an option to the user to disable auto generation of PartnerLinkTypes. By default, the option is selected (i.e. partnerlinktypes are generated).

  • Abstract Configuration Tab in new WSDL Document wizard.
  • Add PortType dialog.

Enhanced dialogs for binding creation

For both of the following, dialogs support binding validation information. For e.g. Soap related WS-I error info. But please note that, wsdl validation still does not validate using ws-i profile. The tooling does not support non-ws-i compliant creation. But the user is free to create one from source view, or from the tree view (by changing values individually from property sheet) and use it.

Refined "Add Binding and Service" from port type.
  • The "Add Binding and Service" action on the port type will provide the user to select an existing service.
  • Also, the user can choose not to create a port at this time, by unselecting a checkbox.
  • Image:GenerateBindingService_WSDLEditor.Specification61.png
  • Image:GenerateBSPNoExistingService_WSDLEditor.Specification61.png
New dialog for "Add Binding" action.</span>
  • Add binding action will provide a user with a dialog, using which the user can select the port type that should be selected to implement.
  • If there is only one port type, then its preselected.
  • User can also choose to create a service port for the created binding.
  • Image:addbinding_WSDLEditor.Specification61.png
  • Image:AddBindingMoreThanOnePortType_WSDLEditor.Specification61.png

Drag and Drop schema/wsdl file into wsdl editor from project explorer to import those into current wsdl.

In both cases, the user can specify the prefix for the import in the dialog that is presented.

DnD of wsdl file nodes from project explorer to current wsdl.</span>

Currently the user needs to use the add Import action to add an wsdl import to a wsdl file. DnD provides an alternative way for user to accomplish the same task. For DnD, following conditions should be met, for the drop to be successful.

  1. WSDL file should be well formed.
  2. WSDL file from same project: Allowed
  3. WSDL File from a referenced project: Allowed
  4. WSDL File from another project which is not a project reference: Not allowed.
DnD of schema file nodes from project explorer to current wsdl.</span>

For DnD, following conditions should be met, for the drop to be successful.

  1. Schema file should be well formed.
  2. Schema file from same project: Allowed
  3. Schema File from a referenced project: Allowed
  4. Schema File from another project which is not a project reference: Not allowed.

the imported schema is added to the default inline schema (which is the schema with the same targetNamespace as the wsdl's. Otherwise a default inline schema is created, and then the import is added.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo