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 6B348200B94 for ; Sun, 2 Oct 2016 11:48:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5E22B160AEA; Sun, 2 Oct 2016 09:48:22 +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 AA017160AD8 for ; Sun, 2 Oct 2016 11:48:21 +0200 (CEST) Received: (qmail 48379 invoked by uid 500); 2 Oct 2016 09:48:20 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 48211 invoked by uid 99); 2 Oct 2016 09:48:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Oct 2016 09:48:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 99F842C2A5F for ; Sun, 2 Oct 2016 09:48:20 +0000 (UTC) Date: Sun, 2 Oct 2016 09:48:20 +0000 (UTC) From: "Sergey Beryozkin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-7057) CXF JAXRSClientFactoryBean proxy async support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 02 Oct 2016 09:48:22 -0000 [ https://issues.apache.org/jira/browse/CXF-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15540107#comment-15540107 ] Sergey Beryozkin edited comment on CXF-7057 at 10/2/16 9:48 AM: ---------------------------------------------------------------- In fact I reckon Dubbot proxy creation code should do what CXF code does - included the custom interface plus Client + InvocationContextAware... Though if we can find a way to get to the invocation handler through a custom interface proxy only then it will be fine, but adding those 2 extra interfaces in Dubbot will make things simpler. was (Author: sergey_beryozkin): In fact I reckon Dubbot proxy creation code should do what CXF code does - included the custom interface plus Client + InvocationContextAware... Though if we can find a way to get to the invocation handler through a custom interface proxy only then it will be fine, but adding those 2 extra interface in Dubbot will make things simpler. > CXF JAXRSClientFactoryBean proxy async support > ---------------------------------------------- > > Key: CXF-7057 > URL: https://issues.apache.org/jira/browse/CXF-7057 > Project: CXF > Issue Type: Wish > Components: JAX-RS > Affects Versions: 3.1.7 > Environment: Linux Mac > Reporter: Neal Hu > Fix For: 3.1.8 > > > Say we have resource interface org.apache.cxf.Resource, and its impl org.apache.cxf.ResourceImpl, we can create client proxy via JAXRSClientFactoryBean as below; > {code:java} > Class type = org.apache.cxf.Resource.class; > JAXRSClientFactoryBean bean = new JAXRSClientFactoryBean(); > bean.setAddress(baseAddress); > bean.setServiceClass(type); > bean.setProviders(providers); > bean.setFeatures(features); > bean.setThreadSafe(true); > T proxy = bean.create(type); > {code} > Then invoke the method via proxy.method1. > As we know the spec client api can invoke via async mode, my question is if the dynamic proxy mode support async mode. > We are developing micro service framework which based on CXF RS, and the comsumer's invoker is dynamicly generated by the clientfactory.create. Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)