Return-Path: 
 <issues-return-24391-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
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 B79BFE952
	for <apmail-cxf-issues-archive@www.apache.org>;
 Mon, 18 Feb 2013 23:29:12 +0000 (UTC)
Received: (qmail 17779 invoked by uid 500); 18 Feb 2013 23:29:12 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 17757 invoked by uid 500); 18 Feb 2013 23:29:12 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 17748 invoked by uid 99); 18 Feb 2013 23:29:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Feb 2013 23:29:12 +0000
Date: Mon, 18 Feb 2013 23:29:12 +0000 (UTC)
From: "Bruce Jones (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12632911.1361230023141.302958.1361230152263@arcas>
In-Reply-To: <JIRA.12632911.1361230023141@arcas>
References: <JIRA.12632911.1361230023141@arcas>
Subject: [jira] [Updated] (CXF-4835) HTTP Conduit configuation not getting
 picked up under CXF 2.7.3
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-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Jones updated CXF-4835:
-----------------------------

    Description: 
When upgrading from CXF 2.1.5 to CXF 2.7.3 it appears the HTTP conduits defined in cxf.xml are no longer used in certain scenarios. The code is quite simple and I am guessing is something to do with a change in the usage of the "name" attribute in the conduit element. I went through all the migration guides and found no mention of this change. The cxf.xml is below:

{code:title=cxf.xml}
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"
       xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
           http://cxf.apache.org/schemas/configuration/http-conf.xsd
           http://www.springframework.org/schema/beans
           http://www.springframework.org/schema/beans/spring-beans.xsd">

	<http-conf:conduit name="https://qa4.paymentexpress.com/WS/PXWS.asmx">
        <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
    </http-conf:conduit>
    <http-conf:conduit name="https://sec.paymentexpress.com/WS/PXWS.asmx">
        <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
    </http-conf:conduit>
</beans>
{code}

This is a publiclly accessable WSDL file available at:
https://qa4.paymentexpress.com/WS/PXWS.asmx?wsdl

Note: the WSDL appears to have 2 ports defined for the same service. Not sure if the conduit configuration is getting confused with this?

If I change the name to *.http-conduit it works but this is obviously not an acceptable solution.

  was:
When upgrading from CXF 2.1.5 to CXF 2.7.3 it appears the HTTP conduits defined in cxf.xml are no longer used. The code is quite simple and I am guessing is something to do with a change in the usage of the "name" attribute in the conduit element. I went through all the migration guides and found no mention of this change. The cxf.xml is below:

{code:title=cxf.xml}
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"
       xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
           http://cxf.apache.org/schemas/configuration/http-conf.xsd
           http://www.springframework.org/schema/beans
           http://www.springframework.org/schema/beans/spring-beans.xsd">

	<http-conf:conduit name="https://qa4.paymentexpress.com/WS/PXWS.asmx">
        <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
    </http-conf:conduit>
    <http-conf:conduit name="https://sec.paymentexpress.com/WS/PXWS.asmx">
        <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
    </http-conf:conduit>
</beans>
{code}

This is a publiclly accessable WSDL file available at:
https://qa4.paymentexpress.com/WS/PXWS.asmx?wsdl

Note: the WSDL appears to have 2 ports defined for the same service. Not sure if the conduit configuration is getting confused with this?

If I change the name to *.http-conduit it works but this is obviously not an acceptable solution.

    
> HTTP Conduit configuation not getting picked up under CXF 2.7.3
> ---------------------------------------------------------------
>
>                 Key: CXF-4835
>                 URL: https://issues.apache.org/jira/browse/CXF-4835
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.6.6, 2.7.3
>         Environment: Windows XP SP3
> Java 7u11
>            Reporter: Bruce Jones
>
> When upgrading from CXF 2.1.5 to CXF 2.7.3 it appears the HTTP conduits defined in cxf.xml are no longer used in certain scenarios. The code is quite simple and I am guessing is something to do with a change in the usage of the "name" attribute in the conduit element. I went through all the migration guides and found no mention of this change. The cxf.xml is below:
> {code:title=cxf.xml}
> <beans xmlns="http://www.springframework.org/schema/beans"
>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>        xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"
>        xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
>            http://cxf.apache.org/schemas/configuration/http-conf.xsd
>            http://www.springframework.org/schema/beans
>            http://www.springframework.org/schema/beans/spring-beans.xsd">
> 	<http-conf:conduit name="https://qa4.paymentexpress.com/WS/PXWS.asmx">
>         <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
>     </http-conf:conduit>
>     <http-conf:conduit name="https://sec.paymentexpress.com/WS/PXWS.asmx">
>         <http-conf:client AllowChunking="false" ProxyServer="localhost" ProxyServerPort="8888" />
>     </http-conf:conduit>
> </beans>
> {code}
> This is a publiclly accessable WSDL file available at:
> https://qa4.paymentexpress.com/WS/PXWS.asmx?wsdl
> Note: the WSDL appears to have 2 ports defined for the same service. Not sure if the conduit configuration is getting confused with this?
> If I change the name to *.http-conduit it works but this is obviously not an acceptable solution.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira