title: com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.lang.ClassCastException
body: <p>I am currently trying to call a JAX-WS from a Weblogic 12c and Java 7 environment. I've generated the client stubs using the weblogic client generator plugin from maven, specifically:</p>
  
  <pre><code>&lt;b&gt;groupId:com.oracle.weblogic&lt;/b&gt;&lt;br&gt;
  &lt;b&gt;artifactId:weblogic-maven-plugin&lt;/b&gt;
  </code></pre>
  
  <p>client jars seem to generate fine. I am able to generate the client stub in java, but when the actual API is called through the stub that will send the SOAP message to the service, I get the following strange exception:</p>
  
  <pre><code>&lt;b&gt;com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
  com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
          at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:131)
          at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:219)
          at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:143)
          at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:138)
          at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:892)
          at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:841)
          at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:804)
          at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:706)
          at com.sun.xml.ws.client.Stub.process(Stub.java:385)
          at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:189)
          at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
          at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
          at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:172)
          at $Proxy130.getSearchResults(Unknown Source)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:601)
          at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)&lt;/b&gt;
  </code></pre>
  
  <p>I saw this same question being posted under a glassfish setup <a href="https://stackoverflow.com/questions/20019316/glassfish-very-strange-classcastexception">Here</a></p>
  
  <p>But with no solution.</p>
  
  <p>Now i've tried SOAP UI, the service responds fine from here, i've tried using weblogic 11g, and same error is produced. I am logging the actual SOAP message that is going out before the exception is produced, and the xml is accurate and works when run from SOAP UI.</p>
  
  <p>What could be causing this?</p>
  
  <p>Thanks </p>