Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 31 May 2016 14:51:12 +0000 (UTC)
From: "Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12974053.1464643996000.337820.1464706272929@Atlassian.JIRA>
In-Reply-To: <JIRA.12974053.1464643996000@Atlassian.JIRA>
References: <JIRA.12974053.1464643996000@Atlassian.JIRA> <JIRA.12974053.1464643996319@arcas>
Subject: [jira] [Assigned] (CXF-6926) StaticSTSProperties does not allow
 initialization of crypto from Properties object
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 31 May 2016 14:51:19 -0000


     [ https://issues.apache.org/jira/browse/CXF-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh reassigned CXF-6926:
----------------------------------------

    Assignee: Colm O hEigeartaigh

> StaticSTSProperties does not allow initialization of crypto from Properties object
> ----------------------------------------------------------------------------------
>
>                 Key: CXF-6926
>                 URL: https://issues.apache.org/jira/browse/CXF-6926
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.1.6
>            Reporter: Andreas Vallen
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 3.1.7, 3.2.0
>
>
> This was working in CXF 3.0.7 courtesy of the getProps method which was removed by git commit 40c9bfd, effective for 3.1 branch.
> The former possibility to set an initialized Properties object was helpful as an adapter to the spring infrastructure for properties (Resource and Environment abstraction, property placeholder and such) instead of relying on an additional external properties file sourced by cxf-specific mechanisms.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)