[esb-issues] [JBoss JIRA] Updated: (JBESB-2711) Verify quickstarts webservice_consumer_wise2 -> webservice_producer

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] David Ward updated JBESB-2711: ------------------------------ Attachment: smooks-request-report.html First off, I did revert some stuff to not mask the initial problem: Revisions 27961 and 27962. Second, it looks to me like the smooks request mapping is being done correctly: a) See attached [smooks-request-report.html] file. On the Result tab you will see the complexObject details. b) In the debugger, I see that the output map in SmooksMapper.java:104 *does* contain the complexObject. What's intersting, then, is why this exception is spit out in the server console when exercising the test: it.javalinux.wise.core.exceptions.WiseRuntimeException: Error during method invocation! at it.javalinux.wise.core.exceptions.WiseRuntimeException.rethrow(WiseRuntimeException.java:44) at it.javalinux.wise.core.client.WSMethod.invoke(WSMethod.java:88) at it.javalinux.wise.core.client.WSMethod.invoke(WSMethod.java:119) at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:251) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:586) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:420) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:545) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: wrong number of arguments 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:585) at it.javalinux.wise.core.client.WSMethod.invoke(WSMethod.java:75) ... 9 more So, the question becomes, "why is WSMethod.invoke having a problem invoking PingWS.java's 'public ComplexObject pingComplexObject(@WebParam(name = "complexObject")' method/operation?" If the SmooksMapper is indeed creating the correct result in applyMapping, why can't WISE map that to the "complexObject" @WebParam? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira