HTTP Receiver

The entry point of most BusinessWorks services. Becomes a platform-http route that accepts every method on the path and only ever sets one fallback response body.

What it does in BusinessWorks

Starts a process when an HTTP request arrives on a configured HTTP Connection shared resource. Request line, headers and body are exposed as the process start type, and whatever the process maps back out through its final Reply activity becomes the response.

The Camel equivalent

from("platform-http:/BookShipment")
    .routeId("orders-BookShipment--http-entry")
    .log(LoggingLevel.INFO,
        "HTTP BookShipment ${header.CamelHttpMethod} ${header.CamelHttpUri}")
    .to("direct:BookShipment")
    .choice()
        .when(simple("${body} == null"))
            .setBody(constant("OK"))
    .end();

Where the semantics diverge

Every HTTP method lands on the same route. The rule does not read whatever method the HTTP Connection shared resource was configured for and never emits httpMethodRestrict. If the original was meant to accept POST only, the generated route currently accepts GET, PUT, anything, on that path, until someone adds the restriction back by hand.

The only response logic this rule writes is a null check. If the process left an empty body, the route substitutes the literal string "OK". Otherwise, whatever body and headers the inner route set are returned as they are, with no explicit status code and no explicit content type: both fall to platform-http’s own defaults. A process that used its Reply activity to set a specific status or content type needs that logic added to the route by hand; the rule does not carry it over, because process starter’s HTTP Connection settings, and the Reply activity’s own mapping, are not what this rule reads.

The path is the process name, not the shared resource’s configured path. path is / followed by the operation name; nothing here reads the HTTP Connection resource’s own path setting, so a service exposed at a different path in BusinessWorks than its process name changes address on migration unless that is corrected by hand.

What the toolchain does

Emits one platform-http route per HTTP starter: a route ID combining the component and operation name, one info-level log line, a hop to the process’s own internal route, and the null-body fallback shown above. Nothing about method restriction, response status, content type or the original HTTP Connection resource’s configured path is read or carried over.