[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] David Ward reassigned JBESB-2711: --------------------------------- Assignee: David Ward -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-2711: ------------------------------------- Just to note Dave... WISE doesn't work on AS5 because it tries to construct its own classloader for wsconsume and it does this based on the assumption that it's running in an AS4 container. This will be resolved in ESB 4.7, with the introduction of the next version of WISE. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-2711: ----------------------------------- Okay, this is the status of this item so far: -> webservice_producer = runs fine on both as4 and as5 -> webservice_consumer_wise3 = runs fine on as4; didn't try as5 due to Tom's comment -> webservice_consumer_wise4 = runs fine on as4; didn't try as5 due to Tom's comment -> webservice_mtom = runs fine on as4, but "ant runtest" dies on as5 with the following console output: runtest: [java] Exception in thread "main" javax.xml.ws.WebServiceException: org.jboss.util.NotImplementedException [java] at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnRequest(ClientSOAPHandlerTube.java:168) [java] at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:100) [java] at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) [java] at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) [java] at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) [java] at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) [java] at com.sun.xml.ws.client.Stub.process(Stub.java:235) [java] at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120) [java] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230) [java] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) [java] at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103) [java] at $Proxy19.echoImage(Unknown Source) [java] at org.jboss.soa.esb.samples.quickstart.webservicemtom.webservice.client.MTOMClient.main(MTOMClient.java:62) [java] Caused by: org.jboss.util.NotImplementedException [java] at org.jboss.ws.core.soap.SOAPPartImpl.appendChild(SOAPPartImpl.java:298) [java] at com.sun.xml.bind.marshaller.SAX2DOMEx.startElement(SAX2DOMEx.java:176) [java] at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:144) [java] at com.sun.xml.ws.message.AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:179) [java] at com.sun.xml.ws.handler.SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:64) [java] at org.jboss.soa.esb.samples.quickstart.webservicemtom.webservice.MTOMProtocolHandler.verifyXOPPackage(MTOMProtocolHandler.java:61) [java] at org.jboss.soa.esb.samples.quickstart.webservicemtom.webservice.MTOMProtocolHandler.handleOutbound(MTOMProtocolHandler.java:48) [java] at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) [java] at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:278) [java] at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:119) [java] at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnRequest(ClientSOAPHandlerTube.java:160) [java] ... 12 more -> webservice_consumer_wise2 = runs *once* on as4 with the svn changes I committed (see further below); didn't try as5 due to Tom's comment Again, on as4, webservice_consumer_wise2 will run *once* fine, but then subsequent invocations reveal this on the server console: 17:06:50,446 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:localhost#queue/quickstart_webservice_consumer_wise2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_webservice_consumer_wise2_esb/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 39b9b7cc-3e1e-4b50-8105-018d295fe8e4 RelatesTo: jms:correlationID#39b9b7cc-3e1e-4b50-8105-018d295fe8e4 $ svn commit Sending webservice_consumer_wise2/build.xml Sending webservice_consumer_wise2/jboss-esb.xml Deleting webservice_consumer_wise2/smooks-config-XMLGregorianCalendar.xml Adding webservice_consumer_wise2/smooks-request-config.xml Sending webservice_consumer_wise2/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer_wise2/MyRequestAction.java Sending webservice_consumer_wise2/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer_wise2/MyResponseAction.java Sending webservice_consumer_wise2/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer_wise2/ComplexObject.java Transmitting file data ...... Committed revision 27856. The most important change was in MyRequestAction.java, where I had to change the requestMap parameter name from "external" to "complexObject", otherwise the WISE client couldn't map the request parameter to PingWS.java's 'public ComplexObject pingComplexObject(@WebParam(name = "complexObject")' method/operation. So in summary, webservice_consumer_wise2 on as4 needs more attention, as does webservice_mtom on as5. If anyone else wants to take a peak, please feel free, otherwise I'll investigate more. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2711: ------------------------------------- I am creating an issue to investigate wise on AS5, just in case there is anything we can do to handle this for 4.6. -- 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

[ 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2711: ------------------------------------- David, as mentioned in the call yesterday we do not have access to that code. It was prior to Stefano's code donation and we do not have access to that repository. Ping me when you are online and we can discuss this further. Either this did not work for 4.5 or something other than wise is likely to have changed. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2711: ------------------------------------- Updated webservice_consumer_wise2 readme.txt to reflect new smooks behaviour. Revision is 28039. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2711?page=com.atlassian.jira.plu... ] David Ward closed JBESB-2711. ----------------------------- Resolution: Done Re-tested all quickstarts on both as4 and as5 after TomF and Kevin's changes - everything now passes. -- 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