Merge origin/master

easybus-rabbitmq/README.MD

@@ -16,24 +16,37 @@ RabbitMQ connection.
     bus.search("me.kisoft.easybus.rabbitmq.test");
 ```
 
-Events can also be attached to specific queues, by using the ```@QueueName``` annotation
+Events can also be attached to specific exchanges, by using the ```@ExchangeName``` annotation
 
 ```java
     @Event
-    @QueueName("named_event")
+    @ExchangeName("exchange.name")
     public class NamedEvent{
         ....
     }
 ```
 
-If no name is given, then the name of the event class itself will be used as the queue name.
+If no name is given, then the name of the event class itself will be used as the exchange name.
+
+
+Event Handlers can also be attached to specific queues, by using the ```@QueueName``` annotation
+
+```java
+    @Handle(event=MyEvent.class)
+    @QueueName("queue.name")
+    public class MyEventHandler{
+        ....
+    }
+```
+
+If no name is given, then the name of the handler class itself will be used as the queue name.
 
 ## Caveats
 
-1. All messages go on the main exchange
-2. Each Event has its own channel open, which might not be optimal in a larger application
+1. ~~All messages go on the main exchange~~ As of 2.2.0, you can use custom exchanges
+2. ~~Each Event has its own channel open, which might not be optimal in a larger application~~ This is generally best practice it seems
 3. Object De/Serialization is done using Jackson, which might not be ideal, and right now,
 there is no way to customize the ```ObjectMapper``` class.
 4. You need Getters/Setters for everything you want to de/serialize
 5. You cant rely on object references - this makes callbacks a little more difficult.
-6. All Queues are destroyable(no persistent queues)
+6. All Queues are destroyable(no persistent queues)