Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 2 Mar 2012 16:59:57 +0000 (UTC)
From: "Andrei Shakirin (Created) (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <1220223275.12622.1330707597280.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CXF-4154) AbstractConduitSelector reused cached
 conduit even if protocol was changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

AbstractConduitSelector reused cached conduit even if protocol was changed
--------------------------------------------------------------------------

                 Key: CXF-4154
                 URL: https://issues.apache.org/jira/browse/CXF-4154
             Project: CXF
          Issue Type: Bug
          Components: Core
            Reporter: Andrei Shakirin
         Attachments: AbstractConduitSelector.patch

Hi,

Actually AbstractConduitSelector.getSelectedConduit() creates and caches conduit in selectedConduit variable. Cached conduit is reused by the next calls.

I see the following problem: if user changed protocol in URI between calls, AbstractConduitSelector still uses cached Conduit even it cannot process new URL. In my case cached HTTP consuit tries to process UDP URL.

Proposal for fix: check if protocol in URL was changed and if yes, close and reset selectedConduit.

Patch is attached.

Regards,
Andrei.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira