Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

Generating WSDL and Schema from a Java Interface

Generating WSDL and Schema from a Java Interface

No WSDL? You can use the New Interface wizard as a quick start to generating the basics of a WSDL.
Generating WSDL and Schema from a Java Interface
Once you have set up your Java project in Process Developer's Project Explorer, you can generate WSDL and schema. A BPEL process requires a WSDL interface, and Process Developer automatically generates it from your Java interface.
Additionally, Process Developer automatically synchronizes the generated WSDL with any changes that you might make to the source Java.
To generate WSDL and schema
:
  1. In your Java orchestration project, create a new BPEL process in the bpel folder.
  2. In Participants view, right-mouse click on Partner Service Provider and select
    New Partner Service Provider
    .
  3. In the
    Partner Service Provider
    dialog, select
    Generate Interface
    .
  4. In the New Interface wizard, select From a Java Interface.
  5. Browse to your Java interface and select it.
  6. Notice that the new WSDL is generated in the wsdl folder of your project.
  7. Select
    Finish
    , and then select
    OK
    in the
    Partner Service Provider
    dialog.
WSDL Generation
The following actions occur when you generate a WSDL and schema from a Java interface:
  • All methods in the Java interface manifest as WSDL operations.
  • All method arguments manifest as top-level XML schema element declarations. The arguments are generated with generic names, such as "argl_string". To generate actual argument names, see Generating Argument Names for Schema Elements.
  • The method return type manifests as a top-level XML schema element declaration.
  • All declared exceptions on the method manifest as WSDL faults.
  • The WSDL is commented with "Do Not Edit" since it is a derived file that can be automatically updated.
The resulting WSDL contains the following constructs:
  • One Partner Link Type named [
    JavaInterfaceName
    ]
    PLT
  • One Port Type named [
    JavaInterfaceName
    ]
  • One Operation within the port type for each method in the Java Interface
  • Two messages for each Java interface method:
    • One message for the method's arguments named [
      methodName
      ] with a single part of the same name.
    • One message for the method's return value named [
      methodName
      ]
      Response
      with a single part of the same name.
  • Two embedded schema elements for each Java interface method:
    • One element to model the Java interface method's arguments named
      methodName
      .
    • One element to model the Java interface method's return value named [
      methodName
      ]
      Response
      .
  • A schema complexType and a schema element for each Java class used by the interface.
Schema Generation
  • Top-level element declarations are created for each of the explicit class references.
  • The implicit declarations manifest as top-level complexTypes and are reused throughout other parts of the schema (if applicable).
More Ways to Generate WSDL and schema
:
Technique to Generate WSDL
Result
In the Interfaces View, select the New Interface toolbar button.
The New Interface Wizard opens for you to select a Java Interface
In the Project Explorer, select the interface from your Java project. From the right-mouse menu, select
Generate WSDL
WSDL and schema are generated in the location you select
From your Java project, drag and drop a Java interface method to the Process Editor canvas
The Create Activity wizard opens so that you not only generate WSDL and schema, you also create a new Web Services activity (such as a receive).
See also:

Back to Top

0 COMMENTS

We’d like to hear from you!