Question

Wrote a ‘webservice’ with Netbeans wizard, runs on glassfish. I added a reference using the wsdl to my .NET client, VB if it makes any difference.

I clearly have no idea what is going on, as I am encountering some brick walls.

The issue is a SoapHeaderException.

System.Web.Services.Protocols.SoapHeaderException: com/mysql/jdbc/Connection
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(
         SoapClientMessage message, WebResponse response, Stream responseStream, 
         Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(
         String methodName,  Object[] parameters)
at WSClient.WSClient.localhost.DatabaseGateService.createCustomerTable(String xml)
          in C:\Project\WSClient\Web References\localhost\Reference.vb:line 40
at WSClient.USAHWSClientConsumer.TestCustomer() in
          C:\Project\WSClient\Client\WSConsumer.vb:line 22

The web service itself is simple:

@WebService()
public class DatabaseGate {
    private MySQLManagerImp manager;

    public DatabaseGate(){
        manager = new MySQLManagerImp();
    }

    @WebMethod(operationName = "createCustomerTable")
    public void createCustomerTable(@WebParam(name = "xml") String xml) {
        manager.createCustomersTable(xml);
    }
}

It takes an xml string, as I did not want to pass in an abomination of arguments.

I attempt to consume the service by simply instantiating the web reference:

Dim ws As localhost.DatabaseWS = New localhost.DatabaseWS
// Create the xml string
Dim qbCustomerQueryRS As String = qbQuery.GetCustomerQueryXML()
Dim processedCustomerXML As String = 
    customerResponseParser.GetAllCustomerDatabaseFriendlyXML(qbCustomerQueryRS)

ws.createCustomerTable(processedCustomerXML)

I’ve tried writing the string in a soap envelope, but still receive the same message. So passing a string is kaputt, as it should be; why would the WS know to parse a string, and simply instantiating and calling the method from the object as if it were local isn’t working the way I think it does.

What is happening?

Answer 1

Sounds like the WSDL references com/mysql/jdbc/Connection, which is not a class known on the .NET side. If you have control over the Web Service, add annotations to avoid serialization of external class references (like com/mysql/jdbc/Connection). If you don’t, simply download the WSDL to a text file, edit it manually to remove such classes/attributes, and re-create the reference pointing to the edited file. You can change the endpoints in Web.config later.