Get rid of the AbstractInvokeStrategy
Closed this issue · 3 comments
prolic commented
We should get rid of the AbstractInvokeStrategy
, the only class extending it is the HandleCommandStrategy
, so there is no need for this abstraction.
codeliner commented
but the AbstractInvokeStrategy
should make it easy to define a userland strategy (from the docs):
If your favorite convention is not there you can easily write your own invoke strategy by extending Prooph\ServiceBus\Plugin\InvokeStrategy\AbstractInvokeStrategy and implementing the canInvoke and invoke methods.
prolic commented
@basz extended it today to create a custom OnEventStrategy, and ran into
troubles, because it uses handler instead of listeners. The strategy has
only like 20 lines of code. Building a custom one is no problem without the
abstract class.
Am 14.01.2017 01:31 schrieb "Alexander Miertsch" <notifications@github.com>:
… but the AbstractInvokeStrategy should make it easy to define a userland
strategy (from the docs):
If your favorite convention is not there you can easily write your own
invoke strategy by extending Prooph\ServiceBus\Plugin\InvokeStrategy\AbstractInvokeStrategy
and implementing the canInvoke and invoke methods.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYEvIVYpfLtsIaUs9_eyLj757fr97W2ks5rR7UDgaJpZM4LixOX>
.
codeliner commented
ok