This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[07:48:56] * ChanServ sets mode: +o temporalfox [08:36:50] <myghty> hey guys :) good morning [08:39:47] <myghty> just a short question, I am just getting started with vert.x and I am curious about those fat jars. If I am right, I develop small microservices as independent projects and then combine them to a fat jar to make them one deployable unit, right? [08:41:56] <myghty> and second question: usually u have like a small chain which requests pass… interface –> controller –> business logic… where to put those start methods? In the interface? Or directly in the controller and leave out the interface completely? [09:02:21] * ChanServ sets mode: +o temporalfox

[10:06:46] * ChanServ sets mode: +o temporalfox [13:19:33] * ChanServ sets mode: +o temporalfox

[14:04:39] <dklotz> A question on (event bus) interceptors: In a local Vert.x, my interceptors get the full message body, in a clustered environment the address, headers etc. are there, but the message body is null (even though the message is sent and received with a message body successfully). Is this deliberate / by design or a bug or do I have to do something special to access the message body in a clustered event bus interceptor?

[15:05:58] * ChanServ sets mode: +o temporalfox [16:15:32] <dklotz> looks like interceptors are not really popular… [16:42:05] <dklotz> (or maybe there's just nobody in a similar timezone like me… :)) [20:02:04] * ChanServ sets mode: +o temporalfox