[CXF-5678] Allow setting custom DestinationRegistry in HTTPTransportFactory

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-milestone2
• Fix Version/s: 3.0
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Alessio Soldano
• Reporter: Alessio Soldano
• Created: 08/Apr/14 10:11
• Updated: 11/Jul/14 12:50
• Resolved: 08/Apr/14 10:20

Description

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:

bus.setExtension(new JBossWSDestinationRegistryImpl(), DestinationRegistry.class);

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.