In the documentation for predefined routs for batched request here Pre-Defined Routes it shows the example of /json/reply/Hello
When I try and post to /json/reply to any service, I get the following error :
{
"responseStatus": {
"errorCode": "NotImplementedException",
"message": "The operation does not exist for this service",
"stackTrace": "System.NotImplementedException: The operation does not exist for this service\r\n at ServiceStack.Host.Handlers.ServiceStackHandlerBase.AssertOperationExists(String operationName, Type type) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack/src/ServiceStack/Host/Handlers/ServiceStackHandlerBase.cs:line 275\r\n at ServiceStack.Host.Handlers.GenericHandler.CreateRequestAsync(IRequest req, String operationName) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack/src/ServiceStack/Host/Handlers/GenericHandler.cs:line 30\r\n at ServiceStack.Host.Handlers.GenericHandler.ProcessRequestAsync(IRequest httpReq, IResponse httpRes, String operationName) in /home/runner/work/ServiceStack/ServiceStack/ServiceStack/src/ServiceStack/Host/Handlers/GenericHandler.cs:line 79\r\n",
"errors": []
}
}
That’s still using the legacy pre-defined routes which don’t exist in Endpoint Routing (e.g. /json/reply|oneway ). The only pre-defined routes are just /api/{RequestDto} for the route, /api/{RequestDto}[] for auto batched requests.
We’re not generating oneway routes in Endpoint Routing due to route pollution of a relatively unused feature. You’d instead need an explicit API for it that just drops the Request DTO in the registered MQ, e.g:
public object Any(QueueHello request)
{
Request.PopulateRequestDtoIfAuthenticated(request);
MessageProducer.Publish(request);
return new EmptyResponse();
}