Implement Continuous behavior with the new scheme
Fix a bunch of related stuff in the process.
Another JSON-friendliness round
This time it could not deserialize due to some private field. Oh,well...
Get rid of charging reason to make life easier with JSON
Unfortunately, the situation with JSON deserialization errors is gettingworse. I knew it, so I should have followed another path. Let me say itonce more:
Never, ever use string-based protocols/formats as your base....
Add rabbitmq.imevents.credit property
Implement Once behavior with the new scheme. Refactor in the process
Fixed RabbitMQProducer. Now it is fully reliable.
Towards a perfect RabbitMQProducer -> actor not receiving msgs
Change var to val
Adhere to existing naming conventions
NOTE: Test integration with the receiving system (Astakos).
WIP charging behavior
View revisions
Also available in: Atom