You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Scott Hilterbrick (JIRA)" <ji...@apache.org> on 2009/10/23 20:14:02 UTC
[jira] Created: (CXF-2494) Follow-Up to bug CXF-1591
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
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.
[jira] Updated: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Scott Hilterbrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Hilterbrick updated CXF-2494:
-----------------------------------
Attachment: doubleit.zip
I've attached a test case with the same issue running under cxf v2.2.3. The password for the sample keystore is "password" and you need to alter the path to the keystore within the serviceKeystore.properties file.
Thanks,
Scott
> 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.
[jira] Commented: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Scott Hilterbrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769347#action_12769347 ]
Scott Hilterbrick commented on CXF-2494:
----------------------------------------
I guess a bit more information may be helpful. I've written a CXF service which receives a SOAP request from an SDK utility. My SOAP response contains the results within the body and also utilizes WS-Security (Timestamp & Signature). I need to also include a wsa:MessageID within the SOAP header and thus have configured my servlet-cxf.xml file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xmlns:soap="http://cxf.apache.org/bindings/soap"
xmlns:wsa="http://cxf.apache.org/ws/addressing"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd">
<jaxws:endpoint
id="search"
implementor="gov.ices.webservice.service.SearchMessageReceiverImpl"
wsdlLocation="WEB-INF/wsdl/sws.wsdl"
address="/search">
<jaxws:outInterceptors>
<bean class="org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor" />
<ref bean="TimestampSign_Response"/>
</jaxws:outInterceptors>
<jaxws:features>
<wsa:addressing/>
</jaxws:features>
</jaxws:endpoint>
<!--
WSS4JOutInterceptor for signing the SOAP response.
-->
<bean id="TimestampSign_Response" class="org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor">
<constructor-arg>
<map>
<entry key="action" value="Timestamp Signature" />
<entry key="user" value="key"/>
<entry key="signaturePropFile" value="serviceKeystore.properties"/>
<entry key="signatureKeyIdentifier" value="DirectReference"/>
<entry key="passwordCallbackClass" value="com.mycompany.webservice.service.ServiceKeystorePasswordCallback"/>
<entry key="signatureParts" value="{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp;{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body"/>
</map>
</constructor-arg>
</bean>
</beans>
The resultant SOAP response contains the body and WS-Security within the header but the WS-Addressing is missing. The only indication of a problem is found within the tomcat logs as a WARNING. Any suggestions?
Oct 23, 2009 1:55:26 PM org.apache.cxf.ws.addressing.ContextUtils retrieveMAPs
WARNING: WS-Addressing - failed to retrieve Message Addressing Properties from context
Thanks,
Scott
> 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
>
> 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.
[jira] Resolved: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2494.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
More or less working as designed and workaround found. Marking resolved.
> 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
> Fix For: Invalid
>
> 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.
[jira] Commented: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769341#action_12769341 ]
Daniel Kulp commented on CXF-2494:
----------------------------------
Please attach a testcase as we have tests that show it working.
> 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
>
> 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.
[jira] Commented: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Scott Hilterbrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770104#action_12770104 ]
Scott Hilterbrick commented on CXF-2494:
----------------------------------------
Dan,
Thanks for the quick reply. I suspected if the client was not sending the WS-A headers then the server would not reply with them either. Within the actual client I'm working with the WS-A headers are included and the server does not respond with the WS-A headers. However, the client code is based on AXIS and I suspect this is why CXF is not responding as anticipated. I will take a look at your second suggestion although I was successful in getting what I needed using the post from http://www.nabble.com/Add-%22out-of-band%22-soap-header-using-simple-frontend-td19380093.html.
Many Thanks,
Scott
> 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.
[jira] Commented: (CXF-2494) Follow-Up to bug CXF-1591
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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.