Alex Gutan

@ppatierno sure. My project kind of requires this functionality anyway, so I'll work on that and submit a pr. Also, what about wildcards? As descibed [here](http://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices). I'm particularly interested in...

@ppatierno yes the client will publish to a well defined topic. suppose the route definition is like this: `Route fooBarRoute = router.route().path("foo/+/bar");` and a client publishes a message on the...

@ppatierno ok let's follow the standards. Then I'll implement the wildcards like this `Route fooBarRoute = router.route().path("foo/+/bar");` and if there is need to get the value of the wildcard, one...

@vietj could you make a separate package for the router files from the vertx-web? A common router package that will be used in vertx-web and vertx-mqtt. I think I've done...

@vietj @pmlopes any updates on this?

@joerg84 Well, I gave up searching for a solution for now, since the issue is not my main priority. Last thing I checked were similar settings to AWS on DigitalOcean....

@joerg84 I followed exactly this instructions: [https://dcos.io/docs/1.10/installing/cloud/digitalocean/](https://dcos.io/docs/1.10/installing/cloud/digitalocean/) Then added Flink from the UI (didnt change the configuration). I also opened a StackOverflow thread two months ago: [https://stackoverflow.com/questions/45391980/error-installing-flink-in-dcos/46262547](https://stackoverflow.com/questions/45391980/error-installing-flink-in-dcos/46262547)

@judithpatudith the issue hasn't been resolved. At joerg84's request I reproduced the issue. Still waiting for it to be addressed.

@joerg84 apparently it did for me.