Maintaining SOAP Extensions

When designing SOAP messages you can edit:

• method data
• parameter data
• table data
• class data
• field data

To specify the format for SOAP messages in the virtual interface editor, do the following:

1. Choose Workbench → Preferences → Java → Templates.
2. Choose SOAP Extensions visible in the virtual interface editor.

Editing Method Data

Select the node SOAP Extensions in the tree component of the Mapping tab. You can make the following entries on the right side of the screen:

• Edit the default namespace of the operation in the field Namespace Name. This value is used for the namespace of request/response elements for document/literal style and for the "namespace" binding attribute value for rpc/literal and rpc/encoded styles.
• Edit the name of the SOAP body element wrapping the operation parameters in the request SOAP message in the SOAP Request Name field.
• Edit the name of the SOAP body element wrapping the operation return type in the SOAP Response Name field.
  Note

  The values of the fields SOAP Request Name and SOAP Response Name are only relevant for DOCUMENT/LITERAL style messaging.

Editing Parameter Data

Choose SOAP Extensions under the incoming or outgoing parameters to change the following parameter option:

• Choose as Header for request parameters, if the parameter will be sent as header in the SOAP Header part of the message. (By default, the parameter will be send as SOAP body parameter.)

  

Editing Table Data

Choose the Types tab and double-click on SOAP Extensions beneath the array name. For complex arrays you can enter the name of the element that will be used in the schema description of the array in the Item Label field.

Editing Class Data

Choose the Types tab and double-click on SOAP Extensions under the name of the class.

• Enter a Local Name in the corresponding field. This value  will be the complex type name in the schema for that class.
• Enter the Namespace Name in the corresponding field. The value will be the namespace of the complex schema type.

  

• Click on Runtime classes in the menu to add a runtime class to the class in question.

  Interfaces and abstract classes occurring anywhere in an endpoint are only allowed, if at least one extending class for runtime behavior is specified.

Editing Field Data

Choose the Types tab and double-click on SOAP Extensions under a type name.

• Choose is Attribute, if the attribute of the type should be described in the schema rather as attribute than as element.

  This feature is available only for simple type properties (int, String, float). By default each property is represented in the schema as element.