[CXF-4811] Allow conduit match pattern to be customized.

• Type: New Feature
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.4.3
• Component/s: Integration
• Estimated Complexity: Advanced
• Assignee: Unassigned
• Reporter: Ivan Latysh
• Created: 05/Feb/13 17:18
• Updated: 02/Jul/15 15:59

Description

Use-case:
Developed jaxrs client has no knowledge of the server URL until it is shipped to a customer.
To address the issue, server name and port has been externalized and handled by a standard PropertyPlaceholderConfigurer:

<jaxrs:client id="serviceClient"
address="http://${server.name}:${server.port}/services/*"/>

<context:property-placeholder/>

<bean class="org.springframework.web.context.support.ServletContextPropertyPlaceholderConfigurer">
		<property name="order" value="1"/>
		<property name="ignoreUnresolvablePlaceholders" value="false"/>
</bean>

But currently http conduit can not be configured as match pattern is set the conduit name, rather than a property.

<cxf-http:conduit name="http://localhost/services.*" />

The best option is to introduce custom URL Matchers, so conduit delegate actual URL matching to a configurable implementation.

Than a simple solution would be to extend org.apache.cxf.configuration.spring.ConfigurerImpl and resolve the property placeholders before compiling the pattern in initWildcardDefinitionMap method. But the poor architectural decisions led to PropertyResourceConfigurer to be non-reusable. It supports rigid visitor pattern, and do not even provide a method to resolve a property placeholder after postProcessBeanFactory has been called.

So the dirty hack would be to configure pattern in the conduit property, rather in the name.

<cxf-http:conduit id="service1Conduit">
  <property name="url" value="http://${server.name}:${server.port}/services/*">
</cxf-http:conduit>

Issue Links

• duplicates: CXF-5320 HTTP Conduits allow for little flexibility when matching against URLs