Expand the Type Explorer tree to locate and select the schema element to use. Select the root element of the XSD file and click OK.

18-30 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 18–29 Type Chooser Dialog 6. Expand the Type Explorer tree to locate and select the schema element to use. If the schema you want to use is not located in the project in which you are working, you can import a schema XSD file or WSDL file into the project using the Import Schema File or Import WSDL icon in the upper right corner of the dialog. After you specify a file, Oracle JDeveloper parses it to determine the defined schema elements and displays them in a list from which you can make a selection.

7. Select the root element of the XSD file and click OK.

The Add Message Part dialog reappears with the URL and Schema Element fields populated from the Type Chooser dialog. If you selected an XSD simple type, these fields are replaced by a Simple Type element.

8. Click OK on the Add Message Part dialog.

The input information appears in the Input field of the Create WSDL dialog. 9. Repeat the above steps to define message parts for the Output and Fault fields. The output represents the response message and is required in synchronous transactions. Faults are optional.

10. Click OK.

To generate a WSDL file for an asynchronous interface from an XSD file: Perform these steps after the Create WSDL dialog appears when you are creating an Oracle Mediator component or when you are defining a service for an Oracle Mediator component. Note: If you want to use a schema XSD file that resides on your local file system, ensure that the XSD file and any XSD files that it imports all reside in the Oracle JDeveloper project directory. This ensures that the schema is deployed with the project and is made available at runtime. Note: Partner link types are generally used in BPEL, so you do not need to select Generate partnerlinkType extension for Oracle Mediator. Getting Started with Oracle Mediator 18-31 1. On the Create WSDL dialog, enter the following information for the WSDL file: ■ File Name : A unique name for the WSDL file. ■ Directory : The directory where you want to store the WSDL file. By default, it is stored in the same location as the Oracle Mediator file. ■ Namespace : A namespace address for the WSDL file; for example, http:oracle.comesbnamespacesMediator. The namespace that you specify is defined as the tns namespace in the WSDL file. ■ Port Type : The name of the port type in the WSDL file that contains the operation to use. ■ Operation : The name of the action to perform; for example, executeQuery.

2. In the Interface Type field, select Asynchronous Interface.

The Input field and Callback section appear, as shown in Figure 18–30 . Figure 18–30 Create WSDL Dialog for an Asynchronous Interface

3. To the upper right of the first Input field, click Add a new message part.

The Add Message Part dialog appears, as shown in Figure 18–31 . Note: Spaces and special characters are not allowed in an operation name or port type. Only alphabetic and numeric characters are supported, and the first character cannot be a number.