Permalink
Browse files

Include architecture diagram into documentation

  • Loading branch information...
krasserm committed Aug 11, 2012
1 parent 1d76e09 commit 4f5b80a941c7512602522cf2846e3d0a5750ed06
View
@@ -1,5 +1,5 @@
Info
----
Overview
--------
This project re-implements [eventsourcing-example](https://github.com/krasserm/eventsourcing-example) based on the Eligosource [Eventsourced](https://github.com/eligosource/eventsourced) library. Regarding library usage, it demonstrates how to
@@ -11,6 +11,11 @@ This project re-implements [eventsourcing-example](https://github.com/krasserm/e
Compared to the [old implementation](https://github.com/krasserm/eventsourcing-example), the whole service and persistence layer are re-written and domain events are now decoupled from the immutable domain model. The web UI and XML/JSON API remain unchanged and are built on top of [Jersey](http://jersey.java.net/), [Scalate](http://scalate.fusesource.org/) and [JAXB](http://jcp.org/en/jsr/detail?id=222). A [Play](http://www.playframework.org/)-based version will follow (which supports asynchronous responses in contrast to Jersey).
Architecture
------------
![Architecture](https://raw.github.com/eligosource/eventsourced-example/master/doc/images/invoice-example.png)
Build
-----
View
BIN -746 Bytes (99%) doc/images/invoice-example.png
Binary file not shown.
@@ -30,7 +30,7 @@ class PaymentGateway(invoiceComponent: Component) extends Actor {
def receive = {
case msg: Message => msg.event match {
case InvoicePaymentRequested(invoiceId, amount, to) => {
// don't use a replay channel but acknowledge immediately
// don't use a reply channel but acknowledge immediately
sender ! Ack
// because payments may take several days to arrive ...

0 comments on commit 4f5b80a

Please sign in to comment.