[esb-issues] [JBoss JIRA] Commented: (JBESB-727) SOAPClient Action & .NET Endpoints
[ http://jira.jboss.com/jira/browse/JBESB-727?page=comments#action_12369465 ]
Tom Fennelly commented on JBESB-727:
------------------------------------
Hi guys.
Yep, I've fixed both of these and will check it all in once I get a chance (now that
the code freeze is over).
So what was the "operation" property will be gone and in it's place will be
the "SOAPAction" property. It can be the same as the old "operation"
property, or a URI ala SOAPAction. It works out the operation from that, so no need to
operation and SOAPAction.
SOAPClient Action & .NET Endpoints
----------------------------------
Key: JBESB-727
URL: http://jira.jboss.com/jira/browse/JBESB-727
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2 Milestone Release 2
Reporter: Burr Sutter
Assigned To: Tom Fennelly
Fix For: 4.2
Attachments: Bad_Request.txt, Good_Request.txt, jboss-esb.xml,
Response_To_Bad_Request.txt, Response_To_Good_Request.txt
Attached are my "traces" from using TcpMon to evaluate why it "fails"
from the ESB but succeeds when using the SoapUI GUI.
Plus attached is my jboss-esb.xml.
The problem appears to be in the SOAPAction HTTPHeader. The ESB SOAPClient action is not
prefixing it with the namespace while the SoapUI GUI tool is and that appears to be the
difference.
In the case of "Bad_Request" if I manually modify the following lines then it
all works. Content-Type had to be added, SOAPAction needed the double quotes and the
namespace.
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://tempuri.org/Greeting"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira