Breakdown of the rest.context Scenario

When a REST Request is sent to the REST-Java-REST App with the HTTP Headers (for example, bookName and bookID) using the SOAPUI project context-REST-Java-REST-soapui-project.xml:

  1. they are mapped to context parameters that can be retrieved in the Java IT Implementation (“Java1 (service-inbound)” in the Runtime Node logs shown later)
  2. new basic header values and a collection of headers is sent to the REST-Java App via context parameters (“Java1 (reference-inbound)” in the Runtime Node logs shown later)
  3. the headers are retrieved in the REST-Java App’s Java IT implementation (“Java2 (service-inbound)” in the Runtime Node logs shown later)
  4. new outbound headers are set in the REST-Java App’s Java IT implementation (basic and bag) to be sent back to the REST-Java-REST App (Java2 (service-outbound) in the Runtime Node logs shown later)
  5. the headers sent by REST-Java App are retrieved in REST-Java-REST App’s Java IT implementation (“Java1 reference-outbound)” in the Runtime Node logs shown later)
  6. some headers are set in REST-Java-REST App’s Java IT implementation to be sent back to the originating client (“Java1 (service-outbound)” or “Java1 (service-fault)” in the Runtime Node logs shown later, depending on the value of “storename” (“success” and “fault” respectively))