[GitHub] [camel-quarkus] dhartford commented on issue #248: Create a Camel Netty TCP extension

dhartford commented on issue #248: Create a Camel Netty TCP extension URL: https://github.com/apache/camel-quarkus/issues/248#issuecomment-547940436 Alright, native tests pass, adding the the reflective classes with an additional dependency camel-endpointdsl was the solution.

[GitHub] [camel-quarkus] dhartford commented on issue #248: Create a Camel Netty TCP extension

dhartford commented on issue #248: Create a Camel Netty TCP extension URL: https://github.com/apache/camel-quarkus/issues/248#issuecomment-547632796 I'll keep moving forward with Socket, thanks for the double-check. I simulated the Poem test from the original camel-netty tests and is

[GitHub] [camel-quarkus] dhartford commented on issue #248: Create a Camel Netty TCP extension

dhartford commented on issue #248: Create a Camel Netty TCP extension URL: https://github.com/apache/camel-quarkus/issues/248#issuecomment-546468763 Pre-review request - I've started doing the integration tests directly with Socket code, which feels incorrect, but I didn't want to burden

[GitHub] [camel-quarkus] dhartford commented on issue #248: Create a Camel Netty TCP extension

dhartford commented on issue #248: Create a Camel Netty TCP extension URL: https://github.com/apache/camel-quarkus/issues/248#issuecomment-54163 Reviewing, I was hoping for a sample init commit of just the netty-http to see what the scope was, but no luck. Reviewing these, let me know