- 05 Feb, 2015 15 commits
-
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Conflicts: .gitignore LICENSE.md README.md
Torkel Ödegaard committed -
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
- 04 Feb, 2015 19 commits
-
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
More work on events, still have to convert pascal case event type name to rabbitmq dot notation, but after that should be done
Torkel Ödegaard committed -
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
- 03 Feb, 2015 6 commits
-
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
Torkel Ödegaard committed
-
If notifications are enabled in the config, Adds a eventHandler accepting Notification{} payloads to the internal Bus. The eventHandler then marshals the payload into json and sends it to a rabbitmq topic exchange using the Notification.Priority+Noticiation.EventType as the routing key. eg. INFO.account.created Currently, notifications are only being emitted for INFO.account.created INFO.account.updated INFO.user.created INFO.user.updated
woodsaj committed
-