{"issue":{"milestone":null,"user":{"id":717985,"login":"rwfowler","url":"https://api.github.com/users/rwfowler","avatar_url":"https://secure.gravatar.com/avatar/7b14a746902333adac308f84427765fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"7b14a746902333adac308f84427765fb"},"title":"Empty body and connectionKey with Akka integration","created_at":"2011-12-13T20:34:35Z","updated_at":"2011-12-18T17:01:57Z","labels":[],"state":"closed","id":2542896,"html_url":"https://github.com/catify/camel-websocket/issues/14","closed_at":"2011-12-18T17:01:57Z","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"I'm using this project to get WebSocket communication to work with an Akka-based app I'm writing. The problem I ran into is that my Akka/Camel consumer gets a message, but the body is null, and the headers are incomplete. I managed to get things working by adding the following code to WebsocketConsumer.java and then disabling the tests in WebsocketConsumerTest.java.\r\n\r\n\r\n```java\r\nexchange.getIn().setHeader(WebsocketConstants.CONNECTION_KEY, connectionKey);\r\nexchange.getIn().setBody(message);\r\n```\r\n\r\nI'm a newbie when it comes to looking at camel component code, but this makes some sense to me. Shouldn't a consumer always be dealing with \"exchange.in\" rather than \"exchange.out\"?\r\n\r\nThanks,\r\nRyan\r\n","number":14,"url":"https://api.github.com/repos/catify/camel-websocket/issues/14","comments":1,"assignee":null},"action":"closed"}