[
https://issues.apache.org/jira/browse/CXF-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-5567.
------------------------------
Resolution: Not A Problem
Fix Version/s: Invalid
Assignee: Daniel Kulp
This is working as expected.
By default, when using the Dispatch style invokations, we don't try to
associate the data with an operation in the WSDL as doing so can break
streaming and take a significant amount of time. There are three ways around
this:
1) When you create the Dispatch, specify an AddressingFeature() to force the
usage of WS-Addressing. To get the correct Action, we have to process the
contents to get an Operation.
2) client.getRequestContext().put("find.dispatch.operation", Boolean.TRUE);
That will force CXF to always patch the dispatch to an operation.
3) client.getRequestContext().put(MessageContext.WSDL_OPERATION, new QName(ns,
"opName");
would force the specific operation name.
> Policy attached to messages input/output of the binding not picked for
> dispatch case.
> --------------------------------------------------------------------------------------
>
> Key: CXF-5567
> URL: https://issues.apache.org/jira/browse/CXF-5567
> Project: CXF
> Issue Type: Bug
> Components: STS
> Reporter: renu gupta
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> I tried to use the sts sample given in CXF samples to write a dispatch client
> using CXF APIs.
> Thread:
> http://cxf.547215.n5.nabble.com/Facing-issue-while-building-STS-Client-USing-Dispatch-API-td5739992.html#a5740102
> And getting These policy alternatives can not be satisfied:
> {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}EncryptedParts:
> {http://schemas.xmlsoap.org/soap/envelope/}Body not ENCRYPTED
> {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SignedParts:
> {http://schemas.xmlsoap.org/soap/envelope/}Body not SIGNED
> at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:84)
>
> What is the alternate to get the input/output policy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
