cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-4811) Allow conduit match pattern to be customized.
Date Thu, 02 Jul 2015 15:51:04 GMT


Sergey Beryozkin commented on CXF-4811:

Trying to build on Dan's idea:

<http:conduitMapper conduit="service1Conduit" url="http://${}:${server.port}/services/*"/>

> Allow conduit match pattern to be customized.
> ---------------------------------------------
>                 Key: CXF-4811
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: Integration
>    Affects Versions: 2.4.3
>            Reporter: Ivan Latysh
>            Priority: Critical
> Use-case:
>   Developed jaxrs client has no knowledge of the server URL until it is shipped to a
>   To address the issue, server name and port has been externalized and handled by a standard
> {code}
> <jaxrs:client id="serviceClient"
> address="http://${}:${server.port}/services/*"/>
> <context:property-placeholder/>
> <bean class="">
> 		<property name="order" value="1"/>
> 		<property name="ignoreUnresolvablePlaceholders" value="false"/>
> </bean>
> {code}
> But currently http conduit can not be configured as match pattern is set the conduit
name, rather than a property.
> {code}
> <cxf-http:conduit name="http://localhost/services.*" />
> {code}
> 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
> {code}
> <cxf-http:conduit id="service1Conduit">
>   <property name="url" value="http://${}:${server.port}/services/*">
> </cxf-http:conduit>
> {code}

This message was sent by Atlassian JIRA

View raw message