Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8649F200B5C for ; Thu, 11 Aug 2016 16:15:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 83A4A160A93; Thu, 11 Aug 2016 14:15:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D235B160A90 for ; Thu, 11 Aug 2016 16:15:16 +0200 (CEST) Received: (qmail 83336 invoked by uid 500); 11 Aug 2016 14:15:16 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 83327 invoked by uid 99); 11 Aug 2016 14:15:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2016 14:15:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A157BC071B for ; Thu, 11 Aug 2016 14:15:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xhIpgVt4GYJo for ; Thu, 11 Aug 2016 14:15:14 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id F272B60E20 for ; Thu, 11 Aug 2016 14:15:13 +0000 (UTC) Received: (qmail 83308 invoked by uid 99); 11 Aug 2016 14:15:13 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2016 14:15:13 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0A870DFBAA; Thu, 11 Aug 2016 14:15:12 +0000 (UTC) From: tillrohrmann To: issues@flink.incubator.apache.org Reply-To: issues@flink.incubator.apache.org Message-ID: Subject: [GitHub] flink pull request #2357: [FLINK-4362] [rpc] Auto generate rpc gateways via ... Content-Type: text/plain Date: Thu, 11 Aug 2016 14:15:12 +0000 (UTC) archived-at: Thu, 11 Aug 2016 14:15:17 -0000 GitHub user tillrohrmann opened a pull request: https://github.com/apache/flink/pull/2357 [FLINK-4362] [rpc] Auto generate rpc gateways via Java proxies This PR introduces a generic `AkkaRpcActor` which receives rpc calls as a `RpcInvocation` message. The `RpcInvocation` message is generated by the `AkkaInvocationHandler` which gets them from automatically generated Java Proxies. The Java proxies are generated in the `AkkaRpcService` class upon connection or starting of a rpc server. R @mxm, @StephanEwen You can merge this pull request into a Git repository by running: $ git pull https://github.com/tillrohrmann/flink proxyRpc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/2357.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2357 ---- commit 13f6f392943e32b14bf0d08c7ded2d88496911ab Author: Till Rohrmann Date: 2016-08-10T16:42:26Z [FLINK-4362] [rpc] Auto generate rpc gateways via Java proxies This PR introduces a generic AkkaRpcActor which receives rpc calls as a RpcInvocation message. The RpcInvocation message is generated by the AkkaInvocationHandler which gets them from automatically generated Java Proxies. Add documentation for proxy based akka rpc service ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---