Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACA9D10C4F for ; Wed, 27 Nov 2013 09:01:55 +0000 (UTC) Received: (qmail 67777 invoked by uid 500); 27 Nov 2013 09:01:54 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 67005 invoked by uid 500); 27 Nov 2013 09:01:49 -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 66846 invoked by uid 99); 27 Nov 2013 09:01:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 09:01:46 +0000 Date: Wed, 27 Nov 2013 09:01:45 +0000 (UTC) From: "Manuel EVENO (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-4702) Make it possible to get global JAX-RS providers registered on the bus 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/CXF-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833590#comment-13833590 ] Manuel EVENO commented on CXF-4702: ----------------------------------- Is there any documentation on how to do this ? > Make it possible to get global JAX-RS providers registered on the bus > --------------------------------------------------------------------- > > Key: CXF-4702 > URL: https://issues.apache.org/jira/browse/CXF-4702 > Project: CXF > Issue Type: Improvement > Components: JAX-RS > Reporter: Sergey Beryozkin > Assignee: Sergey Beryozkin > Fix For: 2.6.5, 2.7.2 > > > Typically, one will register JAX-RS providers on per-endpoint basis; the same provider may also be shared between multiple endpoints; > However in some cases it may be useful to get the same provider shared between endpoints by simply registering the provider on the bus: this also simplifies the configuration of the individual endpoints. > Bus interface offers typed extension API but the changes are needed to this API to make it easy to inject number of extensions from Spring/Blueprint; while it can make it simpler to work at the code level, the benefit at Spring level is minimal, and thus using Bus.setProperties appears to be sufficient at the moment -- This message was sent by Atlassian JIRA (v6.1#6144)