HTTP Rest Adapter - always calling the same Service Interface

[#1]

I have tried to setup a HTTP Rest adapter to take JSON requests. I would like to setup one adapter to handle all the requests from our Hybris system.

For this Rest adapter, I need it to support 4 different calls:

Shipment

Registration

Sample

Request

I tried setting up the Rest adapter with the following settings:

Channel Selection:

Rest Resources:

Rest Operation:

Standard - no changes past default

Operation Determination:

This works to a point. It picks the correct Operation Determination but runs the wrong OM.

Here is a snippet of the log from a Registration attempt:

What am I doing wrong? Any advice?

[Former Member]

I re-read my submission but I don't think I was very clear with the problem. When I try to send a "Registration" transaction to the HTTP REST Adapter, the adapter sees it as a Registration and picks the correct Service Interface.

However the wrong Operation Mapping is actually called. The one that is called is for the Shipment transaction (not the Registration). These are on 2 very different Service Interfaces and Integrated Configuration Objects.

If you can, I am looking for insight into what is going on. I also welcome any suggestions on how to better setup the HTTP Rest adapter.