[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-11707: -------------------------------------- Fix Version/s: (was: 3.3.0.Beta3) (was: 3.3.0.Final) Definitely weird. I'll look into it... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-11707: ------------------------------------------- Brian, now different error is thrown: {code} java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element {http://webservices.samples.jboss.org}sayHello found. Expected {http://webservices.samples.jboss.org/}sayHello. at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element {http://webservices.samples.jboss.org}sayHello found. Expected {http://webservices.samples.jboss.org/}sayHello. at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450) at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381) at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502) at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) {code} Your workaround doesn't work for me, I have been always trying to reselect the operation before clicking Invoke button. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-11707: ------------------------------------------- I'm going to ask a dumb question. Where are you updating the URL in the WSDL? Here? <wsdl:service name="HelloWorldService"> <wsdl:port name="HelloWorldPort" binding="tns:HelloWorldServiceSoapBinding"> <soap:address location="http://localhost:9090/HelloWorldPort"/> </wsdl:port> </wsdl:service> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-11707: ------------------------------------------- Based on my experiences (as I documented in JBIDE-11294), I am able to reproduce the issue and it's that the generated URL included in the soap address of the generated WSDL is incorrect. But during deployment, the issue is resolved and the URL is fixed so it doesn't appear in the deployed WSDL. I'm open to suggestions here, but other than the workaround of updating the soap address, I am out of ideas. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-11707: ------------------------------------------- Today, when I was reproducing the issue, wsdl file which was generated contains this URL of WS service: "http://localhost:9090/HelloWorldPort" but as I remember in Beta3 it was "http://localhost:8080/project/Services/HelloWorld". Weird :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-11707: ------------------------------------------- Yes Brian, I think we should. Thanks for cooperation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11707?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič closed JBIDE-11707. ------------------------------------- As I am not longer able to reproduce the issue I am closing the issue for JBoss Developer Studio 5.0.0 CR1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira