Does #[Priority] Work Across Different Projectors?

[m2mtech]

Hi everyone,

I have two projectors reacting to the same event from one stream. One projector listens solely to this stream (performing primary processing) while the other listens to two streams, relying on the result from the primary one. I tried using #[Priority] to enforce that the single-stream projector runs first, but it appears that the priority is ignored.

Here's a simplified code example:

#[Projecton(SingleStreamProjector::class, PrimaryAgregate::class)]
class SingleStreamProjector
{
    #[Priority(2)]
    #[EventHandler]
    public function onEvent(Event $event): void
    {
        // Primary processing logic
    }
}

#[Projecton(MultiStreamProjector::class, [PrimaryAgregate::class, SecundaryAgregate])]
class MultiStreamProjector
{
    #[Priority(1)]
    #[EventHandler]
    public function onEvent(Event $event): void
    {
        // Processing logic that relies on SingleStreamProjector's output
    }
}

Could it be that #[Priority] only applies within the same projector, or is there another recommended approach to ensure the proper execution order across different projectors?

Note: This question is non-urgent as I've already resolved my issue by using subevents for the low priority projection.

Thanks for any insights!

[dgafka]

@m2mtech just to confirm, do you mean Projection attribute? Because Ecotone doesn't have attribute named Projector :)

And how do you execute those projections synchronous/asynchronous/polling?

[m2mtech]

Sorry ;) - I updated the example

[dgafka]

And how do you execute projections synchronous/asynchronous/polling?

[m2mtech]

synchronous

[lifinsky]

Here, a priority at the projection level is needed, or the event emitter from the primary projection should be used. However, projections generally shouldn't have such dependencies, as they cannot be rebuilt independently.

[jlabedo]

@m2mtech , I think the behavior is now correct since 1.256.0, thanks to changes introduced by #479. Could you confirm ?

[m2mtech]

I agree with @lifinsky that projections really shouldn’t depend on each other. I changed my approach back then and don’t have a suitable setup to check if the changes work with my unfortunate ideas ;)