Playing again with Timestamp check and a stupid exception trick...
To be notified on the server that the WSE2 client has a Timestamp problem (and perhaps doing something like logging the problem), I used this solution on the client:
try
{
proxyWse.DoSomething();
}
catch
{
try
{
proxy.LogError();
throw;
}
catch
{
throw;
}
}
In this way if there is an error with WSE2 the method called on the "normal" proxy succeedes, and then the code re-throws the exception that was generated by WSE2.
If the method called on the "normal" proxy fails, probably there is a connectivity problem, and an exception is thrown.
I don't know if this is the right way, but it works...