Stubbing settings for the Camel transport

You can specify the stubbing settings that depend on the Message Exchange Pattern defined for the Camel transport.

Before you begin

You must have defined a service component and an operation under the service component. See Creating a service component and Creating an operation


  1. Double-click the operation in the Logical View tab of Architecture School perspective.

    The Operation dialog is displayed.

  2. Click the Stub tab.

    The Stub tab is displayed.

  3. Complete the following steps in the Stub tab:
    1. Click Browse in the Binding panel and select Camel as the required transport in the Select a Resource dialog box.
      Note: The name of the transport is the name you provided to the physical resource of the Camel component.
    2. Select from the following options for the action you want:
      Option Action
      No If you select No, you can select any transport in the project.
      Yes If you select Yes, you can select only transports that are referenced (directly or indirectly) by the operation that contains the test.
      Only Direct If you select Only Direct, you can select only transports that are referenced directly by the operation that contains the test.
    3. Click OK.
    4. Select Text as the message type from the list in the Message Type field.
      Note: For messages that are not in the Text format, you must select the Binary option.
    5. Add parameters or headers for the messages that you subscribe that depends on the specifications for the Camel component.
      Note: The Default Timeout section contains common settings for stub replies. No change is required. The response time is managed by the stubs execution engine in HCL OneTest API.
  4. Click OK.


You have configured the stubbing settings in the operation.

What to do next

You can now create stubs based on the stubbing settings for the operation from the Test Factory view.