Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 8 Apr 2014 10:12:15 +0000 (UTC)
From: "Alessio Soldano (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12707148.1396951887926.78611.1396951935566@arcas>
In-Reply-To: <JIRA.12707148.1396951887926@arcas>
References: <JIRA.12707148.1396951887926@arcas>
Subject: [jira] [Created] (CXF-5678) Allow setting custom
 DestinationRegistry in HTTPTransportFactory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alessio Soldano created CXF-5678:
------------------------------------

             Summary: Allow setting custom DestinationRegistry in HTTPTransportFactory
                 Key: CXF-5678
                 URL: https://issues.apache.org/jira/browse/CXF-5678
             Project: CXF
          Issue Type: Improvement
          Components: Transports
    Affects Versions: 3.0.0-milestone2
            Reporter: Alessio Soldano
            Assignee: Alessio Soldano
             Fix For: 3.0.0


I need to set a custom DestinationRegistry implementation in the HTTPTransportFactory (as I override a method in the registry). With CXF 2.7.x, I used to set an instance of my registry impl in the bus:
{noformat}
bus.setExtension(new JBossWSDestinationRegistryImpl(), DestinationRegistry.class);
{noformat}
however that does not work anymore with CXF 3.0 because the HTTPTransportFactory does not hold a reference to the bus anymore, hence it does not look for configured registry in it, and simply creates the default DestinationRegistryImpl.
My idea would be to rely on the optional Configurer which could be installed in the bus (I'm already setting a custom Configurer) to configure the HTTPTransportFactory before it's actually used. The factory is already passed to the configurer afaics. So, we'd need to allow changing the reference to the registry in the factory.


--
This message was sent by Atlassian JIRA
(v6.2#6252)