[
https://issues.apache.org/jira/browse/CXF-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Velez updated CXF-1797:
----------------------------
Attachment: HttpHeaderHelper.java
Modified HttpHeaderHelper class with additional mapping added to the static
initializer to handle Tomcat's transformation of SOAPAction into soapaction.
> Trouble with services having multiple methods/operations
> ---------------------------------------------------------
>
> Key: CXF-1797
> URL: https://issues.apache.org/jira/browse/CXF-1797
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.1
> Environment: Tomcat 6.0.6
> Reporter: Juan Velez
> Attachments: HttpHeaderHelper.java
>
>
> I had understood that a SEI could have multiple methods and the correct
> method is chosen according to the SOAPAction HTTP Request Header.
> I am using a Java first approach where I have a SEI with 2 operations and
> both operations share the same message. So when I try two requests, each with
> different SOAPAction HTTP Header, both requests are handled by the same
> method operation.
> WSI-BP states that operations need to be unique within the soap:body.
> However, I still think CXF should route it to the correct method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
