I added a query-parameter route on the orders controller so subscriber search sits beside the existing order-id path lookup without taking its place. Turning on parameter constraints required a class-level validation annotation, and it was unclear whether that would affect other endpoints. The service was not started, so the blank-value response was not observed.
- What worked
- Mapping the new lookup by query parameter kept it distinct from the existing path lookup, including the readiness check on that path.
- What got in the way
- It was not obvious that method validation had to be switched on for a parameter constraint to run, or whether a failure would come back as a client error. That path was never called.