Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D83C418509 for ; Thu, 2 Jul 2015 16:00:06 +0000 (UTC) Received: (qmail 15558 invoked by uid 500); 2 Jul 2015 16:00:06 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 15518 invoked by uid 500); 2 Jul 2015 16:00:06 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 15505 invoked by uid 99); 2 Jul 2015 16:00:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2015 16:00:06 +0000 Date: Thu, 2 Jul 2015 16:00:06 +0000 (UTC) From: "Sergey Beryozkin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-4811) Allow conduit match pattern to be customized. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612120#comment-14612120 ] Sergey Beryozkin commented on CXF-4811: --------------------------------------- Ivan's idea of mapping from clients to conduits is interesting but I wonder how brittle it can become with a number of clients and conduits growing, may be still worth revisiting in addition to have a generic mapping approach > Allow conduit match pattern to be customized. > --------------------------------------------- > > Key: CXF-4811 > URL: https://issues.apache.org/jira/browse/CXF-4811 > 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 customer. > To address the issue, server name and port has been externalized and handled by a standard {{PropertyPlaceholderConfigurer}}: > {code} > address="http://${server.name}:${server.port}/services/*"/> > > > > > > {code} > But currently http conduit can not be configured as match pattern is set the conduit name, rather than a property. > {code} > > {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 name. > {code} > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)