cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessio Soldano (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5678) Allow setting custom DestinationRegistry in HTTPTransportFactory
Date Tue, 08 Apr 2014 10:22:14 GMT

     [ https://issues.apache.org/jira/browse/CXF-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alessio Soldano resolved CXF-5678.
----------------------------------

    Resolution: Fixed

> 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)

Mime
View raw message