Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1399F18E5A for ; Sun, 24 Jan 2016 17:34:40 +0000 (UTC) Received: (qmail 13013 invoked by uid 500); 24 Jan 2016 17:34:40 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 12989 invoked by uid 500); 24 Jan 2016 17:34:39 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 12980 invoked by uid 99); 24 Jan 2016 17:34:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Jan 2016 17:34:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C94432C1F58 for ; Sun, 24 Jan 2016 17:34:39 +0000 (UTC) Date: Sun, 24 Jan 2016 17:34:39 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-7054) CamelNetty - No way to get ChannelGroup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114394#comment-15114394 ] ASF GitHub Bot commented on CAMEL-7054: --------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/796 > CamelNetty - No way to get ChannelGroup > --------------------------------------- > > Key: CAMEL-7054 > URL: https://issues.apache.org/jira/browse/CAMEL-7054 > Project: Camel > Issue Type: Improvement > Components: camel-netty4 > Affects Versions: 2.12.0, 2.12.1, 2.12.2 > Reporter: Matthew McMahon > Priority: Trivial > Fix For: Future > > > My use case is that I need to create a custom ServerPipelineFactory, and also require access to the ChannelGroup so that I can know when a new channel is being added and when it is removed. > I also sometimes use the channelGroup to send a message to all clients. > In 2.11.1 it was easy to get access to the ChannelGroup through the NettyConsumer. > However with the 2.12.0 restructure this has been hidden behind the NettyServerBootstrapFactory interface. > To get around it for now, I looked at implementing my own NettyServerBootstrapFactory class, but I could not work out how to do that and also use a custom ServerPipelineFactory. Therefore the solution I came up with for now is Reflection! > Basically, I am wondering is it possible to modify the NettyServerBootstrapFactory interface so that the addChannel and removeChannel methods return the boolean from the channelGroup calls. And either provide a getter for the channelGroup, or add a writeAllChannels (bulk write) method interface that does the write method on the channelGroup? -- This message was sent by Atlassian JIRA (v6.3.4#6332)