You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jesse Pangburn (JIRA)" <ji...@apache.org> on 2012/05/23 20:10:40 UTC
[jira] [Created] (CXF-4339) Dispatch client fails to set soap
action header automatically unless WS-Addressing is enabled
Jesse Pangburn created CXF-4339:
-----------------------------------
Summary: Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
Key: CXF-4339
URL: https://issues.apache.org/jira/browse/CXF-4339
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.5.3
Reporter: Jesse Pangburn
Priority: Minor
If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
{quote}
Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
Headers: \{Accept=[*/*]}
Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
{quote}
But when I just disable WS-Addressing then the content-type header changes to the following:
{quote}
Content-Type: application/soap+xml; charset=UTF-8
{quote}
There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
{code}
disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
{code}
So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
--
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
[jira] [Commented] (CXF-4339) Dispatch client fails to set soap
action header automatically unless WS-Addressing is enabled
Posted by "Jesse Pangburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281997#comment-13281997 ]
Jesse Pangburn commented on CXF-4339:
-------------------------------------
Hi Aki,
I'm sorry, I thought the action taken when "find.dispatch.operation" is set to TRUE was the default. I thought it was automatically supposed to resolve this through the WSDL like it does when WS-Addressing is enabled.
Clearly this was my own misunderstanding and not a bug. Again, my apology for filing a bug as I thought this was unintended behavior.
I've verified that after setting that property like this:
disp.getRequestContext().put("find.dispatch.operation", Boolean.TRUE);
Now for SOAP 1.1 and SOAP 1.2 the soap action is set properly with/without WS-Addressing enabled.
I'll close this issue.
thanks,
Jesse
> Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4339
> URL: https://issues.apache.org/jira/browse/CXF-4339
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5.3
> Reporter: Jesse Pangburn
> Priority: Minor
> Labels: client, dispatch, soap
> Fix For: Invalid
>
>
> If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
> {quote}
> Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
> Headers: \{Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
> {quote}
> But when I just disable WS-Addressing then the content-type header changes to the following:
> {quote}
> Content-Type: application/soap+xml; charset=UTF-8
> {quote}
> There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
> {code}
> disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
> {code}
> So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
--
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
[jira] [Closed] (CXF-4339) Dispatch client fails to set soap action
header automatically unless WS-Addressing is enabled
Posted by "Jesse Pangburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Pangburn closed CXF-4339.
-------------------------------
Resolution: Not A Problem
Fix Version/s: Invalid
This was not a bug, it was my own misunderstanding.
> Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4339
> URL: https://issues.apache.org/jira/browse/CXF-4339
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5.3
> Reporter: Jesse Pangburn
> Priority: Minor
> Labels: client, dispatch, soap
> Fix For: Invalid
>
>
> If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
> {quote}
> Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
> Headers: \{Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
> {quote}
> But when I just disable WS-Addressing then the content-type header changes to the following:
> {quote}
> Content-Type: application/soap+xml; charset=UTF-8
> {quote}
> There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
> {code}
> disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
> {code}
> So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
--
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
[jira] [Commented] (CXF-4339) Dispatch client fails to set soap
action header automatically unless WS-Addressing is enabled
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282008#comment-13282008 ]
Aki Yoshida commented on CXF-4339:
----------------------------------
Hi Jesse,
it's okay, no problem.
This ticket reminded me that we need to document this behavior in the dispatcher documentation.
thanks.
regards, aki
> Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4339
> URL: https://issues.apache.org/jira/browse/CXF-4339
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5.3
> Reporter: Jesse Pangburn
> Priority: Minor
> Labels: client, dispatch, soap
> Fix For: Invalid
>
>
> If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
> {quote}
> Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
> Headers: \{Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
> {quote}
> But when I just disable WS-Addressing then the content-type header changes to the following:
> {quote}
> Content-Type: application/soap+xml; charset=UTF-8
> {quote}
> There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
> {code}
> disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
> {code}
> So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
--
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
[jira] [Commented] (CXF-4339) Dispatch client fails to set soap
action header automatically unless WS-Addressing is enabled
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281969#comment-13281969 ]
Aki Yoshida commented on CXF-4339:
----------------------------------
Hi,
are you setting the operation in the request context? (i.e. MessageContext.WSDL_OPERATION)?
If not and if no addressing is enabled, the payload-based operation finding is only triggered if the request context's property find.dispatch.operation is set to Boolean.TRUE. It is not set by default. Could you check if either of these approaches is taken?
Thanks.
regards, aki
> Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4339
> URL: https://issues.apache.org/jira/browse/CXF-4339
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5.3
> Reporter: Jesse Pangburn
> Priority: Minor
> Labels: client, dispatch, soap
>
> If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
> {quote}
> Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
> Headers: \{Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
> {quote}
> But when I just disable WS-Addressing then the content-type header changes to the following:
> {quote}
> Content-Type: application/soap+xml; charset=UTF-8
> {quote}
> There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
> {code}
> disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
> {code}
> So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
--
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
[jira] [Updated] (CXF-4339) Dispatch client fails to set soap
action header automatically unless WS-Addressing is enabled
Posted by "Jesse Pangburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Pangburn updated CXF-4339:
--------------------------------
Description:
If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
{quote}
Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
Headers: \{Accept=[*/*]}
Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
{quote}
But when I just disable WS-Addressing then the content-type header changes to the following:
{quote}
Content-Type: application/soap+xml; charset=UTF-8
{quote}
There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
{code}
disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
{code}
So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
was:
If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
{quote}
Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
Headers: \{Accept=[*/*]}
Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
{quote}
But when I just disable WS-Addressing then the content-type header changes to the following:
{quote}
Content-Type: application/soap+xml; charset=UTF-8
{quote}
There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
{code}
disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
{code}
So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4339
> URL: https://issues.apache.org/jira/browse/CXF-4339
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5.3
> Reporter: Jesse Pangburn
> Priority: Minor
> Labels: client, dispatch, soap
>
> If I have a Dispatch client and I have WS-Addressing enabled on it and I send a request then I see the following:
> {quote}
> Content-Type: application/soap+xml; *action="urn:ihe:iti:2007:RegistryStoredQuery"*
> Headers: \{Accept=[*/*]}
> Payload: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:RegistryStoredQuery</Action>
> {quote}
> But when I just disable WS-Addressing then the content-type header changes to the following:
> {quote}
> Content-Type: application/soap+xml; charset=UTF-8
> {quote}
> There's no action attribute any more. Manually setting the soap action uri on the dispatch object puts it back:
> {code}
> disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
> {code}
> So there's a workaround possible (where your dispatch use case can accommodate it) but the problem is that CXF shouldn't require WS-Addressing enabled to set the Content-Type header's action attribute automatically.
> This is a bigger problem in SOAP 1.1 where many services rely on the SOAPAction header and CXF is sending a blank SOAPAction header by default unless WS-Addressing is enabled.
--
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