Demis thanks for your suggestions. I’m trying to explain how we use your framework.
we have created a service framework, based on your ServiceStack, for the management of business engines on heterogeneous domains. To reduce the time it takes to create, customize, and manage, we’ve built some base classes for services, business logic, and repositories. In some of these classes we have our own implementation that exploits the potential of AutoQuery to allow searches with dynamic filters (we love AutoQuery and its potential - it only lacks the AndOr search mix that is required in some scenarios). Up to ServiceStack version 5.8.0, our Request objects like this
public class QueryLogsRequest : QueryDb<Log, LogDto>
they used namedConnectionAttribute to query the data on the database table corresponding to the NamedConnection. These days we are updating old apps that used version 5.8.0 with version 5.12.0. This is how we discovered that the behavior is no longer like that of version 5.8.0. Given the tight deadlines we solved by marking the domain entities (classes that map the database through OrmLite) with that attribute by removing it from the Request DTOs.
public class Log: DomainEntityWithDescription
So it works but limits us some highly dynamic scenarios that we have rewritten using a custom attribute that reads a header in the Request in which we find the name of the NamedConnection.
I hope you’ll get the big picture clearer. Preparing a repo in GitHub, these days it is not really possible (too busy with updates and little time to do it). Maybe later we could think about it.