Could do with overloading one of the methods on a .NET service i'm currently writing. I can define a seperate MessageName:="xxx" attribute for the methods but then .NET 3.5 throws "Service 'Durbs.WebService' does not conform to WS-I Basic Profile v1.1. Please examine each of the normative statement violations below..."
I can sort this by changing:
<System.Web.Services.WebServiceBinding(ConformsTo: =WsiProfiles.BasicProfile1_1)>
to
<System.Web.Services.WebServiceBinding(ConformsTo: =WsiProfiles.None)>
And all seems happy when consumed via the browser and SoapUi.
But, it still shows warnings in the browser about this BasicProfile1_1 non-conformance
Is this going to cause me any problems with any particular consumers? Is there a reason why that WsiProfiles thing prohibits it? Can't see anything wrong with doing it (and i'm sure earllier .NET didnt complain), but for all I know, this is a big no-no in Java or something?
I can sort this by changing:
<System.Web.Services.WebServiceBinding(ConformsTo: =WsiProfiles.BasicProfile1_1)>
to
<System.Web.Services.WebServiceBinding(ConformsTo: =WsiProfiles.None)>
And all seems happy when consumed via the browser and SoapUi.
But, it still shows warnings in the browser about this BasicProfile1_1 non-conformance
Is this going to cause me any problems with any particular consumers? Is there a reason why that WsiProfiles thing prohibits it? Can't see anything wrong with doing it (and i'm sure earllier .NET didnt complain), but for all I know, this is a big no-no in Java or something?
Comment