[
https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770065#action_12770065
]
Daniel Kulp commented on CXF-2494:
----------------------------------
I believe this is "working as designed". On the server side, the response
message will only get WS-A headers added if the incoming message has ws-a
headers. In your case, the client doesn't send any WS-A headers and thus the
server would not respond with any.
Two options:
1) Turn on ws-a on the client. That would cause the client to send ws-a
headers and the server to response in kind.
2) In you service, you can inject the WebServiceContext and add to the context:
AddressingPropertiesImpl addProp = new AddressingPropertiesImpl();
addProp.setMessageId(.......);
ctx.put("javax.xml.ws.addressing.context.outbound", map);
(that outbound might be inbound to "fake" the inbound headers, not really sure).
> Follow-Up to bug CXF-1591
> -------------------------
>
> Key: CXF-2494
> URL: https://issues.apache.org/jira/browse/CXF-2494
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.2.2
> Environment: Windows XP, Tomcat 5.5,
> Reporter: Scott Hilterbrick
> Attachments: doubleit.zip
>
>
> I'm having the identical problem as reported in CXF-1591. I've tried using
> CXF v2.2.2, v2.2.3 & v2.2.4 but obtain the same errors as reported in
> CXF-1591. Any help you can provide would be greatly appreciated.
> Regards,
> Scott
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
