[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-10-02 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-537444206 4495866 does just `s/QuarkusPlatformHttpEngine.LOG/LOG/` This is an

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-10-01 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-537211134 Is this good to merge now? This is an automated message from the Apache Git

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-10-01 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-537007793 In e66f2326c7bd4662dff548e7ba6272e2f1cd3668 all requests should be either resolved or should have followup issue.

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-10-01 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-537005707 I removed the methods from the URI body after @lburgazzoli mentioned that we could eventually want to have this as a producer, where we

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-10-01 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-536943986 > BTW, this component should be usable from the rest dsl so it may need some further development Yes, there are many things missing,

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-27 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-535971108 3dcfa9a should fix the test failure. This is an automated message from the

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-27 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-535884193 7ccc04d removes the synchromization in the QuarkusPlatformHttpConsumer lifecycle methods.

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-17 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-532290135 f99d4f6 solves the native image test problems. @lburgazzoli are there still some open questions from your PoV?

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-16 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531850873 A simple `vertx-web` itest hangs also on plain Quarkus, but only in 0.22.0 branch. It works on the master. I filed

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-13 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531369582 bdaeb18 adds the mojos to the component module. I still have to figure out why the native test is timing out.

[GitHub] [camel-quarkus] ppalaga commented on issue #201: Fix #184 Leverage platform http service

2019-09-13 Thread GitBox
ppalaga commented on issue #201: Fix #184 Leverage platform http service URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531364334 39fcf89715a847d28f4e53e6f0f20734608710f2 : Addressed most of the points by @lburgazzoli . The native mode test is timing out saying