Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

Designer

Designer

Generating Argument Names for Schema Elements

Generating Argument Names for Schema Elements

When you generate a WSDL file, as described in
Generating WSDL and Schema from a Java Interface
, a method’s argument are generated as schema elements. The elements have generic names, such as
arg1_string
, as shown:
<xs:element form="unqualified" name="arg1_string" type="xs:string"/>
You can generate schema elements with the actual argument names by adding a JAR file called
ae_rt.jar
to the project's Java build path list of external jars and adding annotations to your interface prior to generating the WSDL.
To generate argument names:
  1. In the Project Explorer, right-mouse click on your project, and select
    Properties > Java Build Path
    .
  2. Select the Libraries tab.
  3. Select
    Add External JARs
    .
  4. Browse to [
    Designer Installation
    ]
    \designer\plugins\org.activebpel.enginep_
    [
    version_number
    ]
    \server\shared\lib
  5. Select
    ae_rt.jar
    , as shown:
  6. Open your Java interface file and add the
    @AeWsdlParam
    annotation to each argument. For example:
    Public interface IMyInterface {    public void execute(    @AeWsdlParam("someValue") String someValue); }
  7. Generate (or regenerate ) a WSDL by right-mouse clicking on a Java interface, and selecting
    Generate WSDL
    .
Process Developer generates the schema element with the argument name; for example:
<xs:element form="unqualified" name="someValue" type="xs:string"/>
Notes:
  • You should not edit the generated WSDL. If you update the Java interface, you must regenerate the WSDL.
  • You do not need to deploy
    ae_rt.jar
    . It is already on the server's
    classpath
    .
  • If you upgrade Process Developer to a new version, you must remove the older version of
    ae_rt.jar
    and re-add the new one.

0 COMMENTS

We’d like to hear from you!