Scoped lifetime dependency not working on class implementing ILocalEventHandler

[martinkraan]

Is there an existing issue for this?

• I have searched the existing issues

Description

When creating a handler for a localevent implementing the interface ILocalEventHandler and registering the handler for DI, only transient and singleton work as expected, scoped lifetime does not.

Reproduction Steps

using System.Threading.Tasks;
using Volo.Abp.DependencyInjection;
using Volo.Abp.EventBus;

namespace AbpDemo
{
    public class MyHandler()
        : ILocalEventHandler<StockCountChangedEvent>,
          IScopedDependency
    {
        public async Task HandleEventAsync(StockCountChangedEvent eventData)
        {
             // When multiple events occur in the same request we get a new instance of MyHandler for every event handled here
        }
    }
}

Expected behavior

Expected behaviour is that the lifetime scope of the request is applied to the eventhandler.

Actual behavior

No response

Regression?

No response

Known Workarounds

No response

Version

8.2.0

User Interface

Common (Default)

Database Provider

EF Core (Default)

Tiered or separate authentication server

None (Default)

Operation System

Windows (Default)

Other information

No response

[maliming]

hi

It is not supported IScopedDependency currently.

The Handler class is not be activated in an HTTP request.
for example, the RabbitMQ is used to subscribe to the message and process the event.

[martinkraan]

Hi,

that's unfortunate it is not supported.

You state that the Handler class is not to be activated in a HTTP Request, but I would assume that the local events (Domain Events) published in the aggregateroot or entity that are processed by the ABP framework when the changes are saved to the database are executed in the same scope and not in a new scope! The local events are handled inside the UoW so I would think that they should also be in the same scope.

[maliming]

hi

If you have two local events, the execution order will be one by one.

So we can't get all events, create a scope, and execute them in the same scope.