Messaging: Camel + ActiveMQ Configuration added
Merge branch 'devel' into feat-messaging
added controller and jsp for testing the messaging system
OwnerProtocolNeedService Client changed to support messaging
- introduction of JMSBased implementation of OwnerProtocolNeedService interface.
- createNeed now sends works based on JMS
- JMS based messaging for createNeed, activate and connect methods.
- Content based routing on the owner side
- 1 queue per method on the node side.
- Node-Node messaging
- Node-Owner messaging
- Node-Owner messaging
-Service Refactoring
-sendInOutMessage methods for URI,String replaced with a generic method
-Debugging. Connect,open methods.
-Node-node connect
- dynamic node-node routing
- NeedProtocolActiveMQService added
-Node-node connect
- dynamic node-node routing
- NeedProtocolActiveMQService added
-Owner-Node messaging endpoint negotiation
-Owner-Node messaging endpoint negotiation
- selenium test cases
- some minor changes
Merge branch 'devel' into feat-messaging

Conflicts:
	webofneeds/won-core/src/main/java/won/protocol/service/NeedManagementService.java
	webofneeds/won-core/src/main/java/won/protocol/util/NeedBuilder.java
	webofneeds/won-core/src/main/java/won/protocol/util/NeedModelBuilder.java
	webofneeds/won-owner-webapp/src/main/java/won/owner/web/connection/ConnectionController.java
- some minor changes