rodolfof@blog

Great work! Thanks alot!

does this work with other policy assertions?

I get an error with a certificate assertion...

<processingStep description="Entering SOAP filter Microsoft.Web.Services3.Design.MutualCertificate11Assertion+ClientOutputFilter" />
<processingStep description="Exception thrown: WSE910: An error happened during the processing of a response message, and you can find the error in the inner exception. You can also find the response message in the Response property."> at Microsoft.Web.Services3.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
at Microsoft.Web.Services3.Security.SecurityTokenServiceClient.RequestSecurityToken(SecurityTokenMessage request, String methodName)
at Microsoft.Web.Services3.Security.SecurityContextTokenServiceClient.RequestSecurityContextToken(AppliesTo appliesTo)
at Microsoft.Web.Services3.Security.SecurityContextTokenServiceClient.IssueSecurityContextToken(AppliesTo appliesTo)
at Microsoft.Web.Services3.Security.Tokens.SecurityContextTokenManager.RequestTokenFromIssuer(EndpointReference tokenIssuer, String tokenType, AppliesTo appliesTo, Policy policy, SoapProtocolVersion soapVersion, StateManager messageState, StateManager operationState, StateManager sessionState)
at Microsoft.Web.Services3.Security.SecureConversationClientSendSecurityFilter.EstablishSecureConversation(SoapEnvelope envelope)
at Microsoft.Web.Services3.Security.SecureConversationClientSendSecurityFilter.SecureMessage(SoapEnvelope envelope, Security security)
at Microsoft.Web.Services3.Security.SendSecurityFilter.ProcessMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope envelope)</processingStep>

When ws-compression is used together with MutualCertificate11Assertion and establishSecurityContext is set true, ws-compression compresses RequestSecurityTokenResponse then MutualCertificate11Assertion get wrong token. I am looking for the solution other than setting establishSecurityContext false.

Today I upgrade WS-compression for WSE3 with a new constructor in the class CompressionAssertion. This constructor allows to set the compression policy by code without necessity of configuration file. Thanks to Kenny Lamoot for this idea.

In sample project, the policy file cannot be loaded, it gives this error:

Failed parsing the policy document. Could not load file or assembly 'WSCompression' or one of its depenencies.

What am I missing??

Ihave developed a new WS-Compression implementation for WCF. Thiscode is based on the WSE 3.0 implementation

Any readme? Does the DLL automatically Compress any WebMethods that get called from the WebService?

I have used a previous WSCompression from http://weblogs.asp.net/pglavich/archive/2004/01/24/62475.aspx and it required an attribute to be put on each method.

Surely it isn't as easy as just enabling WSE3 on both projects (Client and WebService) and place the DLL in references?

If you could just pop me a quick hullo to itsupport {@} ntd.com.au that would be great. I just wish the whole compression thing was a "built-in" part of the Framework. But people like you guys make our lives sooo much easier.

Cheers,

Michael Proctor

Thanks for the excellent work!

can u give me a example for multi parater on client side ... ?

because I am a beginner.

BTW, sorry for my poor English.

I dont kown how to write a function in AppClient.cs which has multi parameter.

[SoapMethod( "SomeOperation" )]
public string SomeOperation( string data1, string data2, int count )
{
// ????
}

-----------------------------------------
http://prototypes.shockbyte.com.ar/misc/WSCompression3.zip

Nearly there, still having issues though, I finally worked out the bits and pieces I was missing out of your example.

I have set:
WebService side :-
1) copied the policyCache.config to the root of the webservice
2) Added to the web.config
<microsoft.web.services3>
<diagnostics>
<trace enabled="true" input="inputtrace.webinfo" output="outputtrace.webinfo"/>
</diagnostics>
<policy fileName="policyCache.config"/>
</microsoft.web.services3>
3) Added the attribute to the webservice class
<Policy("ServerPolicy")> _
4) Added references to the WSCompression.DLL
5) Added to the webservice class file
Imports WSCompression
Imports Microsoft.Web.Services3
Imports Microsoft.Web.Services3.Messaging

Then in the client
1) copied the policyCache.config to the root of the appliccation
2) Added into the app.config
<microsoft.web.services3>
<diagnostics>
<trace enabled="true" input="inputtrace.webinfo" output="outputtrace.webinfo"/>
</diagnostics>
<policy fileName="policyCache.config" />
</microsoft.web.services3>
3) Added to the startup class in my app
<Policy("ClientPolicy")> _
4) Added to main class
Imports Microsoft.Web.Services3
Imports WSCompression


Now I get soap header compression was not understood exception when I try and invoke a webmethod, any ideas?

I think I just noticed my problem however I have no idea how to fix it :(

In your test app it the policy attribute isn't on the main app but the actually SOAP client itself, the problem I have is I use WSDL to have my SOAPClient generated. How can I have the Web Reference that gets updated by WSDL to have this attribute. I cannot seem to find the code for the proxy class in the project.

Thanks for your help.

I think I may have worked it out, except I am having problems with the WSE3 addin for VS2005, I noticed on some other websites about using servicewse.setpolicy for policy assertion on proxy generated classes. the drama is my VS2005 is doing the wse3wsdl so I am only getting service and no option for servicewse, I have just tried re-installing and trying to get this to work however I think that will solve the problem, thanks again for your help and if you have any suggestions please drop me a line. ta

Firstly, thank you for this work!

But please can I urge you to make a few simple updates to the download that could make this project much more useful to other developers, and save a lot of time.

These would be:

1. An example showing how a client application can call a web service method that has multiple parameters e.g.
public string SomeOperation( string param1, Class1 param2 )

2. A complete Web service, complete with all necessary files - for example, Test Site references Service.ashx but it is not included.

Many thanks.

A very good job done…
Kindly get us few hints for how to support the implementation of multiple parameter method call using your AppClient code…

Hey guys, it&amp;#39;s been a while. Easy questions, I want to compress the&#160;data sent over the wire but haven&amp;#39;t

Hi

Is it possible to have optional compression? I.e. the server gives the client the option of using compression, the client does not neccesarily have to use the option.

Regards

Gavin

I got this working great... thx, was not to hard to implement. Before I tried this, I tried to get iis 6.0 compression to work for me. Got responses to compress, but could not figure out how to compress the upload myself, so I implemented this instead and works great.