Bug 779889 (SOA-2248) - Riftsaw is unable to invoke .NET web services.
Summary: Riftsaw is unable to invoke .NET web services.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2248
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: riftsaw
Version: 5.1.0 Dev,5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-01 14:28 UTC by Marek Baluch
Modified: 2011-02-18 01:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-18 01:48:44 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2248 0 None None None Never

Description Marek Baluch 2010-09-01 14:28:37 UTC 
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2010-09-01 14:29:13 UTC 
Link: Added: This issue depends RIFTSAW-279
Comment 2 John Graham 2010-09-30 19:55:08 UTC 
See linked project JIRA.
Comment 3 Marek Baluch 2010-10-01 10:41:29 UTC 
Verified on SOA 5.1 ER2.
Comment 4 David Le Sage 2011-02-11 04:15:42 UTC 
Temporarily reopening to update release note info.
Comment 5 David Le Sage 2011-02-11 04:19:33 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/RIFTSAW-279

Riftsaw was unable to invoke .Net web services.  This was because the .NET server did not know how to interpret the SOAPAction header if the latter was set to an empty string. To bypass this issue, the SOAPAction header is now set to the value of the operation.
Comment 6 Dana Mison 2011-02-18 01:48:44 UTC 
this is the first time we have shipped this so it does not have to be documented with resolved issues in the release notes
Comment 7 Dana Mison 2011-02-18 01:48:44 UTC 
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required
Note You need to log in before you can comment on or make changes to this bug.