From the droolsbundle, we are using our interface to access the event bus, which is mocked by EventBusMock, but when we post a command on it, there is no ESH to process that command, and apply the correct state for the Item (to keep the test case minimal). Currently, there is a workaround, so the mock object applies the state to the Item from the command, which is good in the most of the cases, but not a fully featured implementation, like ESH.
Maybe finding out how ESH handles this procedure, and using only that module is enough.
From the droolsbundle, we are using our interface to access the event bus, which is mocked by EventBusMock, but when we post a command on it, there is no ESH to process that command, and apply the correct state for the Item (to keep the test case minimal). Currently, there is a workaround, so the mock object applies the state to the Item from the command, which is good in the most of the cases, but not a fully featured implementation, like ESH.
Maybe finding out how ESH handles this procedure, and using only that module is enough.