Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 13 Jul 2012 15:39:35 +0000 (UTC)
From: "Aki Yoshida (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <1689510273.48653.1342193975154.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (CXF-4423) more flexibility in configuring
 httpconduit's tlsClientParameters in spring and blueprint
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aki Yoshida created CXF-4423:
--------------------------------

             Summary: more flexibility in configuring httpconduit's tlsClientParameters in spring and blueprint
                 Key: CXF-4423
                 URL: https://issues.apache.org/jira/browse/CXF-4423
             Project: CXF
          Issue Type: Bug
          Components: Transports
    Affects Versions: 2.6.1
            Reporter: Aki Yoshida
            Assignee: Aki Yoshida
             Fix For: 2.7.0


Introducing optional ref attributions in the configuration schema to allow the keyManagers and trustMangers to be constructed elsewhere and be assigned to the http conduit's tlsClientParameters using the ref="mybean" notation.

For the background information to this feature, refer to
http://cxf.547215.n5.nabble.com/more-flexibility-in-configuring-httpconduit-s-tlsClientParameters-in-spring-or-blueprint-tc5710607.html


--
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