[
https://issues.apache.org/jira/browse/CXF-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-4315:
--------------------------------
Assignee: Daniel Kulp
> CXF does not read decoupled destination parameters from a config file
> ---------------------------------------------------------------------
>
> Key: CXF-4315
> URL: https://issues.apache.org/jira/browse/CXF-4315
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Kirill Kadyrko
> Assignee: Daniel Kulp
>
> Hi,
> When I try to use WS-RM and put all parameters into the config file, CXF does
> not set up decoupled destination, although it's specified there:
> {code:xml}
> <http:conduit name="{http://someaddr}ServiceName.http-conduit";>
> <http:client DecoupledEndpoint="http://localhost:9015/dec_endpoint"/>
> </http:conduit>
> {code}
> However, when the decoupled destination address is set explicitly in the
> code, everything works OK:
> {code:java}
> Client client = ClientProxy.getClient(port);
> HTTPConduit conduit = (HTTPConduit) client.getConduit();
> HTTPClientPolicy clientPolicy = conduit.getClient();
> clientPolicy.setDecoupledEndpoint("http://localhost:9015/decoupled_endpoint";);
> {code}
> The problem was exposed after migration from CXF 2.4.1 to CXF 2.6.0, so
> everything should be alright with the config files. Also, you can look at
> /samples/ws-rm from the CXF binary distribution. This demo does not fetch the
> destination address from the config file, since all client messages contain
> anonymous _ReplyTo_ address:
> {code:xml}
> <ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>
> </ReplyTo>
> {code}
> Instead of:
> {code:xml}
> <ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> <Address>http://localhost:9990/decoupled_endpoint</Address>
> </ReplyTo>
> {code}
> Same demo runs fine on CXF 2.4.
--
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
