Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS WSDL Editor User's Guide Java CAPS Documentation |
Prerequisites for This Tutorial
Using Code Completion in WSDL Files
Importing XML Schemas Using the WSDL View
Adding Inline Schemas Using the WSDL View
To Configure the Global Properties of the Inline Schema
To Define the Structure of the Inline Schema
Importing WSDL Files Using the WSDL View
Configuring Messages Using the WSDL View
To Change the Name of a Message or Part
Configuring Port Types Using the WSDL View
To Add an Operation to an Existing Port Type
To Add a Fault to a Request-Response Operation
To Change the Name of a Port Type or Operation
To Change the Parameter Order of an Operation
To Delete a Port Type or Operation
Configuring Bindings Using the WSDL View
To Create a Binding and Service from a Port Type
To Create a Binding Individually
Configuring Services Using the WSDL View
To Create a Binding and Service from a Port Type
To Create a Service Individually
Configuring Partner Link Types Using the WSDL View
To Add a Partner Link Type Automatically
To Add a Partner Link Type Manually
Configuring Properties and Property Aliases Using the WSDL View
To Add a Property to a WSDL File
To Add a Property Alias to a WSDL File
Finding Usages of WSDL Components
To Find Usages of a WSDL Component
To Clear Highlights After a Search
Strategies for Defining the Abstract Elements
To Define the Abstract Elements by Starting with the Partner Interactions
To Define the Abstract Elements by Starting with the Messages
Navigating in the Partner View
Creating Partner Link Types Using the Partner View
To Create a Partner Link Type with One Role
To Add a Second Role to a Partner Link Type
To Add a Fault to a Request-Response Operation
Editing Partner Link Types Using the Partner View
To Change the Name of a Partner Link Type, Role, Port Type, or Operation
Creating Messages Using the Partner View
Editing Messages Using the Partner View
To Change the Name of a Message
This section contains the following topics
When you create a WSDL file from scratch, the wizard contains three pages that you can fill out.
The Name and Location page prompts you to enter basic information about the WSDL file.
The Abstract Configuration page prompts you to define the port type, operation, and messages.
The Concrete Configuration page prompts you to define the binding, service, and port.
You do not need to complete all three pages. You can fill out the Name and Location page and then click Finish, or you can fill out the Name and Location page and the Abstract Configuration page and then click Finish.
You cannot enter a name that already exists in the project.
The target namespace appears in the root element.
The WSDL types are:
Abstract WSDL Document — The abstract type only requires that you fill out the Abstract Configuration page of the wizard.
Concrete WSDL Document — The concrete type requires you to select a Binding and a Binding Type. Additional configuration pages are added to the wizard, associated with the binding and type you select.
In the Abstract Configuration wizard page, do the following:
The WSDL file is created. The WSDL Editor appears in WSDL view.
Instead of creating a WSDL file from scratch, you can create a WSDL file based on an existing WSDL file.
To create a WSDL file based on a running service:
Select the From URL button.
Enter the URL of the service's WSDL file.
Click Finish.
To create a WSDL file by using an existing WSDL file on the local file system:
Select the From Local File System button.
Specify the folder where the WSDL file is located.
Click Finish.
The WSDL file is created. The WSDL Editor appears in WSDL view.
XML Schema includes a data type called NCName.
Any name that has the NCName data type must comply with the following rules:
The name must begin with a letter or an underscore (_).
The valid characters for the remainder of the name are:
Letters
Digits
Period (.)
Hyphen (-)
Underscore (_)
You can perform refactoring by using the following approaches:
Rename — Enables you to rename all occurrences in the associated XSD, WSDL, and BPEL files.
Safely Delete — Enables you to check for references to the component before you perform the delete.
Undo — After performing a Rename or Safely Delete action, you can undo that action.
Redo — After performing an undo of a Rename or Safely Delete action, you can redo that action. Menu that shows the refactoring options
You can also rename a component by changing the value of the Name property. The WSDL Editor renames all occurrences in the same file, but not in other files.
The WSDL Editor includes a validation tool. The validation tool reviews the WSDL file for problems with syntax and semantics.
The Output window displays any errors or warnings.