Excellent!
Many thanks for the advice, I realized that is pretty easy to do. I'll give it a shot...
By the way, you have done great work on ABP!
Best regards.
Thanks for your response.
I'm not able to handle that way because using of message queue is mandatory in our case. This strenght comes from an architectural definition for server-to-server integration. While server is running it pushes messages to queue for notifications that must be processed on another one (last one on top of aspnetboilerplate)
Maybe a good starting point is to create a queue consumer registered as singleton, injecting IoCResolver on it. At at time a message is received, I must be able to set up a DbContext, UnitOfWork, set current tentant, etc., and then invoke app service class to do their job.
Please, let me know if I am o the correct way.
Many thanks.
Which is the best way to handle incoming events from external sources, like message queuing, since we don't have a current context available, I mean I want to process those messages inside a correct ABP context in terms of unit of work, localization manager, inject repositories, managers, etc.
I was looking around BackgroundManager implementation to have a hint on this way, but I'm not sure if I'm on the right way.
Many thanks in advance, and thanks for your great work!