You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2013/07/23 08:40:49 UTC
[jira] [Commented] (CXF-5148) can't use property place holder in
http:server|http:client with blueprint
[ https://issues.apache.org/jira/browse/CXF-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716157#comment-13716157 ]
Freeman Fang commented on CXF-5148:
-----------------------------------
The reason here is that currently use AbstractBPBeanDefinitionParser.mapElementToJaxbProperty to unmarshal HTTPClientPolicy|HTTPServerPolicy object and put the object in PassThroughMetadata which has no capability of replacing properties, should use ValueMetadata instead.
Create a HTTPClientPolicyHolder and HTTPServerPolicyHolder class which can play with filtered DOM string should be the way to go, just like JettyHTTPServerEngineFactoryHolder do
> can't use property place holder in http:server|http:client with blueprint
> -------------------------------------------------------------------------
>
> Key: CXF-5148
> URL: https://issues.apache.org/jira/browse/CXF-5148
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
>
> some configuration like
> {code}
> <cm:property-placeholder persistent-id="org.apache.servicemix.examples">
> <cm:default-properties>
> <cm:property name="ReceiveTimeout" value="1"/>
> <cm:property name="contentType" value="my-content"/>
> </cm:default-properties>
> </cm:property-placeholder>
> <http-conf:destination
> name="*.http-destination">
> <http-conf:server ReceiveTimeout="${ReceiveTimeout}"
> ContentType="${contentType}"/>
> </http-conf:destination>
> {code}
> or
> {code}
> <http:conduit id="identificationConduit" name="*">
> <http:client ConnectionTimeout="${connect-timeout}"
> ReceiveTimeout="${read-timeout}" />
> </http:conduit>
> {code}
> The placeholder here never get replaced.
--
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