Comments on: .NET: MTOM Enabled Your Application Using WSE

By: Leng Keng

Leng Keng — Sun, 05 Oct 2008 19:31:23 +0000

If you made changes to the proxy classes, you should remove the web reference and start anew. After the web reference is added back, try to use the one with class name ‘xxxWse’ to ensure that MTOM is enabled.

If the xxxWse class is still missing, you can click on “view all files” icon in the Solution Explorer, then navigate to the reference.cs file of your web reference. Manually change both the proxy class definition and method definition to public from abstract. Finally, change the class to inherit from ‘Microsoft.Web.Services3.WebServicesClientProtocol’ instead of ‘System.Web.Services.Protocols.SoapHttpClientProtocol’. Hope this helps.

By: Mucahid Uslu

Mucahid Uslu — Thu, 21 Aug 2008 16:00:54 +0000

After install Microsoft WSE 3.0, you must add to project reference Microsoft.Web.Services3.

Mucahid Uslu

By: Haris

Haris — Thu, 10 Jul 2008 20:06:28 +0000

“Sometimes the proxy class for WSE is not generated.”

I am facing the same problem.

Does this mean that Client is not configured properly or is it have something to do with Web Service???

Please advise.

By: Keith Losset

Keith Losset — Fri, 06 Jun 2008 15:18:56 +0000

While not using WSE would certainly be a problem, an exhaustive search of WSE839 errors tells me that there are many people that are using WSE30 properly (with the settings you suggest) that get the same or a similar error. In fact, based on the web searches, it is not clear that anyone is able to get MTOM interop to work between a NET 2.0/WSE 3.0 client and any Java-based server side implementation.

Your article is by far the most encouraging. I am curious what success stories or follow-up comments you or your readers might have?