views:

131

answers:

1

We have a SOAP Web Service we wrote that accepts work fine testing without a WSE policy set on the class using the Policy Attribute on the class that implements the WS

"<Policy("ServicePolicy")> _"

once we put the policy in place and the WS is posted to, the service returns back a SoapFault saying (without ever getting into our code, so we are thinking its the WSE/SOAP/.Net plumbing)

" Exception thrown: Header http://schemas.xmlsoap.org/ws/2004/08/addressing%3AAction for ultimate recipient is required but not present in the message."

we have found the below link which is the issue we are having and the suggestion of removing the "<requireActionHeader />" from the policy and still get same error.

http://social.msdn.microsoft.com/Forums/en-US/asmxandxml/thread/1d8017d4-591a-48e4-9ad6-5c29d5978c07

We have also found many article about moving to WCF instead of WSE but at this time we can't due to sender's unwillingness to change their process, so that's out (for now?)

Just wondering if anyone has some suggestions on resolving this. If there's any other information you need to help us, let me know and I will get it for you.

A: 

My suggestion would be that you stop using obsolete software (WSE) and use WCF instead.

If nothing else, you'll probably find many more developers who know WCF than who know WSE.

John Saunders
as I posted in my question"We have also found many article about moving to WCF instead of WSE but at this time we can't due to sender's unwillingness to change their process, so that's out (for now?)"so this "answer" was completely pointless.
MikeScott8
Why would the sender need to change anything? If they are following the standard, then WCF will "just work".
John Saunders