New factory which correctly wraps the event store.

[lunetics]

We now added a default EventStoreFactory and a default ActionEventEmitterFactory.

Event Store

As discussed, imho we should not abstract too much in the symfony implementation. Building some wrapper around the event store creation feels cumbersome and is imho unneded. A user just have to configure his own event store.

  Prooph\EventStore\Pdo\PostgresEventStore:
        arguments:
            - '@Prooph\Common\Messaging\FQCNMessageFactory'
            - '@event_store.pdo_connection'
            - '@Prooph\EventStore\Pdo\PersistenceStrategy\PostgresAggregateStreamStrategy'

this service will be used in the store configuration under the "event_store" key (before: type)

The DefaultEventStoreFactory now wraps (if configured) the configured EventStore in an (Transactional)ActionEventEmitter.

The DefaultActionEventEmitterFactory wraps either ActionEventEmitterEventStore or TransactionalEventEmitterEventStore, depending if TransactionalEventStore is implemented by the EventStore

ActionEventEmitter

The event_emitter config key now only accepts and validates a string of the classname (FQCN) which implements the ActionEventEmitter interface.

So now it's possible to build an own ActionEventEmitterFactory with a custom ActionEventEmitter implementation

Some ideas:

• Also add the plugin check (implements) into the compilerpass (earlier detection)
• Give the option to also have a custom event_emitter factory for each store (service / class?)

[vilnitsky]

Does it mean the minimal requirement is Symfony 3.3 now? Probably we should stick to LTS versions i.e. 2.8 until 3.4 is released.

[sandrokeil]

@lunetics Can we support Symfony 2.8 too?

[codeliner]

Switched back to Symfony\Component\DI
thx @vilnitsky for the hint