You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Juan Velez (JIRA)" <ji...@apache.org> on 2008/09/12 18:23:44 UTC
[jira] Created: (CXF-1797) Trouble with services having multiple
methods/operations
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
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.
[jira] Resolved: (CXF-1797) Trouble with services having multiple
methods/operations
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1797.
------------------------------
Resolution: Fixed
Fix Version/s: 2.1.3
2.0.9
Assignee: Daniel Kulp
Patch applied. Thanks!
> 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
> Assignee: Daniel Kulp
> Fix For: 2.0.9, 2.1.3
>
> 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.
[jira] Updated: (CXF-1797) Trouble with services having multiple
methods/operations
Posted by "Juan Velez (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-1797) Trouble with services having multiple
methods/operations
Posted by "Juan Velez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630617#action_12630617 ]
Juan Velez commented on CXF-1797:
---------------------------------
There is a "mapping" missing in the org.apache.cxf.helpers.HttpHeaderHelper class:
internalHeaders.put("soapaction", "SOAPAction");
This needs to be as part of:
static {
internalHeaders.put("Content-Type", "content-type");
internalHeaders.put("Content-ID", "content-id");
internalHeaders.put("Content-Transfer-Encoding", "content-transfer-encoding");
internalHeaders.put("Transfer-Encoding", "transfer-encoding");
internalHeaders.put("Connection", "connection");
internalHeaders.put("authorization", "Authorization");
}
> 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
>
> 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.