Can I use a WCF client proxy as a straight replacement for SoapHttpClientProtocol?

I'm talking with a web service with a开发者_如何学Go generated proxy that uses System.Web.Services.Protocols.SoapHttpClientProtocol, is there any reason I might have trouble replacing the proxy with a WCF client proxy?

The web service being called is written in Java and uses the Apache Axis SOAP engine. It uses only HTTP Basic authentication.

Is there an underlying issue that you're trying to solve by making this change? I've issues doing something like this in the past.