Web Services binding: Server responses lack WS-Security header / Client doesn't check WS-Security header

If the server framework and the client library are loaded by the same classloader, either the server responses lack WS-Security headers or the client doesn't check WS-Security header. There is a conflict in the WS tube setup. This is not an issue if only the server framework or the client library is used.

Both issues are not critical because they only improve interoperability with a few web services frameworks. Most clients and severs don't notice it. Nevertheless, it should be fixed for maximum interoperability.