You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implementation for the CommandBus, the QueryBus and the EventBus in PHP 7.
6
+
Implementation for the CommandBus, the QueryBus and the EventBus in PHP 7 and using PSR-11.
7
7
8
8
---
9
9
@@ -157,7 +157,7 @@ final class RegisterUserHandler implements CommandHandler
157
157
158
158
I'm assuming you're using some kind Service Container. Now it's time to register your CommandHandler.
159
159
160
-
For instance, in a `Interop\Container` compliant Service Container, we can do this as follows:
160
+
For instance, in a `Psr\Container` compliant Service Container, we can do this as follows:
161
161
162
162
```php
163
163
<?php
@@ -186,9 +186,9 @@ For custom strategies, you may write your own implementing the `NilPortugues\Mes
186
186
187
187
Classes implementing this interface will be resolving the class for the instance required based on the output of the CommandTranslator used.
188
188
189
-
This package provides an implementation, `NilPortugues\MessageBus\CommandBus\Resolver\InteropContainerResolver`, that expects any Service Container implementing the `Interop\Container` interface.
189
+
This package provides an implementation, `NilPortugues\MessageBus\CommandBus\Resolver\PsrContainerResolver`, that expects any Service Container implementing the `Psr\Container` interface.
190
190
191
-
For custom strategies, such as Symfony Container, you may write your own implementing the `NilPortugues\MessageBus\CommandBus\Contracts\CommandHandlerResolver` interface.
191
+
For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: `NilPortugues\MessageBus\CommandBus\Resolver\SymfonyContainerResolver`. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.
192
192
193
193
#### 1.1.5 - Registering the remaining CommandBus classes
@@ -354,7 +354,7 @@ class UserQueryResponse implements QueryResponse
354
354
355
355
I'm assuming you're using some kind Service Container. Now it's time to register your QueryHandler.
356
356
357
-
For instance, in a `Interop\Container` compliant Service Container, we can do this as follows:
357
+
For instance, in a `Psr\Container` compliant Service Container, we can do this as follows:
358
358
359
359
```php
360
360
<?php
@@ -382,10 +382,9 @@ For custom strategies, you may write your own implementing the `NilPortugues\Mes
382
382
383
383
Classes implementing this interface will be resolving the class for the instance required based on the output of the QueryTranslator used.
384
384
385
-
This package provides an implementation, `NilPortugues\MessageBus\QueryBus\Resolver\InteropContainerResolver`, that expects any Service Container implementing the `Interop\Container` interface.
386
-
387
-
For custom strategies, such as Symfony Container, you may write your own implementing the `NilPortugues\MessageBus\QueryBus\Contracts\QueryHandlerResolver` interface.
385
+
This package provides an implementation, `NilPortugues\MessageBus\QueryBus\Resolver\PsrContainerResolver`, that expects any Service Container implementing the `Psr\Container` interface.
388
386
387
+
For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: `NilPortugues\MessageBus\QueryBus\Resolver\SymfonyContainerResolver`. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.
389
388
390
389
#### 2.1.5 - Registering the remaining QueryBus classes
@@ -627,7 +626,7 @@ final class SendWelcomeEmailHandler implements EventHandler, EventHandlerPriorit
627
626
628
627
I'm assuming you're using some kind Service Container. Now it's time to register your Event Handlers.
629
628
630
-
For instance, in a `Interop\Container` compliant Service Container, we can do this as follows:
629
+
For instance, in a `Psr\Container` compliant Service Container, we can do this as follows:
631
630
632
631
```php
633
632
<?php
@@ -671,9 +670,9 @@ Its implementation can be found at: `NilPortugues\MessageBus\EventBus\Translator
671
670
672
671
Classes implementing this interface will be resolving the class for the instance required based on the output of the EventTranslator used.
673
672
674
-
This package provides an implementation, `NilPortugues\MessageBus\EventBus\Resolver\InteropContainerResolver`, that expects any Service Container implementing the `Interop\Container` interface.
673
+
This package provides an implementation, `NilPortugues\MessageBus\EventBus\Resolver\PsrContainerResolver`, that expects any Service Container implementing the `Psr\Container` interface.
675
674
676
-
For custom strategies, such as Symfony Container, you may write your own implementing the `NilPortugues\MessageBus\EventBus\Contracts\EventHandlerResolver` interface.
675
+
For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: `NilPortugues\MessageBus\EventBus\Resolver\SymfonyContainerResolver`. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.
677
676
678
677
#### 3.1.6 - Registering the remaining EventBus classes
0 commit comments