You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2011/07/11 14:53:59 UTC
[jira] [Commented] (CXF-3569) One service port and one soapAction
[ https://issues.apache.org/jira/browse/CXF-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063315#comment-13063315 ]
Aki Yoshida commented on CXF-3569:
----------------------------------
Hi Tomasz,
I tried to reproduce this problem with CXF 2.3.2. and spring 2.5.5,
But I could not reproduce the problem.
Do we have a mail thread on the cxf users mailing list where this problem has been discussed so that I can get more information about your specific setup? If not, could you attach a test case so that we can see this problem?
Thanks.
Regards, aki
> One service port and one soapAction
> -----------------------------------
>
> Key: CXF-3569
> URL: https://issues.apache.org/jira/browse/CXF-3569
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.3.2
> Environment: AIX, WebSphere7.0, spring 2.5
> Reporter: Tomasz Gieszczyk
> Assignee: Aki Yoshida
>
> Hi
> I have generated service client using cxf tools from wsdl file which contains three soapActions. While i create one instance of service and use it for invoking three different methods cxf always sends in header soapAction from method that was invoked first time. For example:
> Methods:
> 1. invokeA - soapAction = invokeA
> 2. invokeB - soapAction = invokeB
> 3. invokeC - soapAction = invokeC
> first action is invokeB, valid request with soapAction=invokeB, second action is invokeC, invalid request with soapAction=invokeB
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira