[
https://issues.apache.org/jira/browse/CXF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943516#comment-13943516
]
Daniel Kulp commented on CXF-5601:
----------------------------------
This is due to a difference in behavior between the Spring parsing and
Blueprint parsing that was never ported from Spring to Blueprint. In spring,
all calls to the "mapElementToJaxbProperty" involve writing the element to a
string and using a factory to parse the string later after Spring has done the
place holders. The blueprint side needs to do the same thing. I'm working
on it.
(this may then eliminate the need for the strange holder things)
> Blueprint property placeholder does not work with http conduit configuration.
> -----------------------------------------------------------------------------
>
> Key: CXF-5601
> URL: https://issues.apache.org/jira/browse/CXF-5601
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.7.7
> Environment: Linux, Karaf 2.3.2
> Reporter: Carma Robot
> Assignee: Daniel Kulp
> Attachments: sts-test-system-2.zip
>
>
> I cannot setup an HTTP conduit configuration that uses the Apache Aries
> Blueprint property-placeholder to inject trust store parameters. The conduit
> works when I explicitly configure the trust store properties. Unfortunately,
> when I use placeholders it fails.
> Please see.
> http://cxf.547215.n5.nabble.com/Blueprint-property-placeholder-does-not-work-with-HTTP-conduit-configuration-td5740946.html#a5741062
> I will also attach my code.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
