facebook

JAX-WS generated client doesn’t work but WS Explorer does

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #298430 Reply

    togath
    Member

    I have a .NET web service that I am trying to connect to with a JAX-WS generated client (Generated with the client wizard). The client generates fine but when I try to call the SOAP method on the server It gives me an exception (See below)

    avax.xml.ws.WebServiceException: org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperException: java.lang.IllegalArgumentException: argument type mismatch
    at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:174)
    at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:69)
    at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:127)
    at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.marshalRequest(DocLitWrappedMethodMarshaller.java:469)
    at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:321)
    at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:159)
    at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:141)
    at $Proxy24.moveOrder(Unknown Source)
    at com.ancestry.dna.admin.UserReconcile.createNewDnaUser(UserReconcile.java:613)
    at com.ancestry.dna.admin.UserReconcile.createNewUser(UserReconcile.java:734)
    at com.ancestry.dna.admin.UserReconcile.reconcile(UserReconcile.java:120)
    at com.ancestry.dna.admin.AdminUtil.reconcileRGCustomerData(AdminUtil.java:163)
    at com.org.struts.action.AdminPageAction.execute(AdminPageAction.java:158)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperException: java.lang.IllegalArgumentException: argument type mismatch
    at org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperToolImpl.wrap(JAXBWrapperToolImpl.java:157)
    at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.marshalRequest(DocLitWrappedMethodMarshaller.java:447)
    … 27 more
    Caused by: java.lang.IllegalArgumentException: argument type mismatch
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.axis2.jaxws.utility.PropertyDescriptorPlus.setAtomic(PropertyDescriptorPlus.java:180)
    at org.apache.axis2.jaxws.utility.PropertyDescriptorPlus.set(PropertyDescriptorPlus.java:158)
    at org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperToolImpl.wrap(JAXBWrapperToolImpl.java:147)
    … 28 more

    I then decided to try the hitting the same web service using the Web Service Explorer. Which successfully connects and makes a successful SOAP method call to the server.

    What is the difference between what the WSE uses and what gets generated by JAX-WS? I would have thought they would have been similar.

    Thanks for the help

    Austin

    #298434 Reply

    togath
    Member

    I was able to fix it. The client was having some issues with some of the Web Servicese included XSDs and was using JAXBElement<String> for a String which was causing the Type Mismatch. I changed my web service to use a different Serializer and that fixed the issue.

    #302454 Reply

    @togath wrote:

    I was able to fix it. The client was having some issues with some of the Web Servicese included XSDs and was using JAXBElement<String> for a String which was causing the Type Mismatch. I changed my web service to use a different Serializer and that fixed the issue.

    Hi, I am also getting the same error. Can you please clarify details of your solution?
    Did you change wsdl, webservice code or client side code?
    If you changed Serializer how did you specify new Serializer?

    I am working with thirdparty web service and I only have WSDL. When I generate code using RAD/Eclipse I get above error when calling the ws via stub interface…

    Thanks,
    Robert

    #304996 Reply

    duguma
    Member

    This message has not been recovered.

    #307577 Reply

    togath
    Member

    In the interface you have a attribute I just used [XmlSerializerFormat]

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: JAX-WS generated client doesn’t work but WS Explorer does

You must be logged in to post in the forum log in