[
https://issues.apache.org/jira/browse/CXF-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601651#action_12601651
]
Daniel Kulp commented on CXF-1623:
----------------------------------
I'll have to dig into the code some more to figure out a correct fix, but I'll
try to answer the questions...
1) Possibly. It may depend on what is needed to get the fix in place.
2) In JAXWS, the binding (soap/xml) and the transport (http) are merged into a
single string. In CXF, they are completely separate so that things like SOAP
over JMS and stuff can properly be modeled. Thus, that code maps the JAX-WS
merged binding into the form we need that just says "soap" so the proper CXF
binding can be picked up. That code is probably "correct", although it's
possible that it should be set to "http://schemas.xmlsoap.org/wsdl/soap/";
instead of "http://schemas.xmlsoap.org/soap/";. If that is done, I think your
use case would work fine as the name.contains(id) would actually pass.
> Wrong
> org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.protocolMatches()
> method implementation or preconditions
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-1623
> URL: https://issues.apache.org/jira/browse/CXF-1623
> Project: CXF
> Issue Type: Sub-task
> Reporter: Richard Opalka
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
