- This topic has 12 replies, 2 voices, and was last updated 9 years, 9 months ago by support-swapna.
-
AuthorPosts
-
neilrichardsParticipantHi,
Wondering what my project is missing that this option is not available. I’m using MyEclipse Enterprise Workbench 10.1.
Any help gratefully received!
Thanks,
Neil Richards
support-swapnaModeratorNeil,
The ‘Import WSDL’ is part of the Web Services support in MyEclipse for Spring tooling. I assume you are working with MyEclipse Professional Edition and that is why the ‘Import WSDL’ wizard is not available.
The usual way to create a web service from WSDL, in MyEclipse, is to create a Web Service Project. Right click on the project, select New, Other, then select MyEclipse->Web Services->Web Service. In the wizard, leave the defaults in the first page and click Next. On the next page, select “WSDL File” and browse to the WSDL you want to use and enter the Java package in which generated files will be placed. Click Next and then Finish. This will use all defaults and generate the code for the web service. You can deploy the project to a web server and test the web service using the Web Services Explorer.
Let us know if you have any questions.
neilrichardsParticipantHi Swapna,
Thanks for your reply. You are right I was using MyEclipse Professional Edition. While I was waiting for a reply I have now installed MyEclipse 2015 CI 10 btw. Some of my projects have the ‘Import Wsdl’ option available, but some don’t – and I can’t seem to find what the difference is.
Anyway, I did what you suggested. On created the project, the WebServices Framework defaulted to JAX-RS and when I used that there was no import from wsld file option available, so I used JAX-WS instead. On generating the classes though in the way you suggest I got a warning: ‘SOAP port WebServicesSoap12: uses a non-standard SOAP 1.2 binding’. I ignored this but when I deployed the project I got the following error:
INFO: WSSERVLET12: JAX-WS context listener initializing Feb 05, 2015 10:36:07 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized SEVERE: WSSERVLET11: failed to parse runtime descriptor: Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" com.sun.xml.ws.server.ServerRtException: Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" at com.sun.xml.ws.server.EndpointFactory.generateWSDL(EndpointFactory.java:415) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:196) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253) at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147) at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4994) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5492) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1247) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1897) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Feb 05, 2015 10:36:07 AM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4994) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5492) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1247) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1897) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: com.sun.xml.ws.server.ServerRtException: Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" at com.sun.xml.ws.server.EndpointFactory.generateWSDL(EndpointFactory.java:415) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:196) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253) at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147) at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108) ... 13 more Feb 05, 2015 10:36:07 AM org.apache.catalina.core.StandardContext startInternal SEVERE: Error listenerStart Feb 05, 2015 10:36:07 AM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [/WebSvcGen] startup failed due to previous errors
Am I doing something wrong?
Thanks,
Neil
support-swapnaModeratorNeil,
Sorry that you are seeing this issue.
What application server are you deploying the project to ?
https://www.genuitec.com/products/myeclipse/learning-center/ws/adding-libraries-build/
Some servers, like Jetty or Tomcat, do not implement the entire Java EE spec and need the JAX-WS libraries deployed with your project.
Please check this tutorial for more details : https://www.genuitec.com/products/myeclipse/learning-center/ws/adding-libraries-build/
If you are still seeing issues even after adding the jars, please share the wsdl with us to help us replicate the issue at our end.
Let us know how it works for you.
neilrichardsParticipantHi Swapna,
I am deploying using the embedded Tomcat server which I believe comes with the JAX-WS libraries pre-installed.
Not allowed to attach wsdl files it seems, so here it is below:
<?xml version="1.0" encoding="utf-8"?> <wsdl:definitions xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://oceanfile.com/webservices/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://oceanfile.com/webservices/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <wsdl:types> <s:schema elementFormDefault="qualified" targetNamespace="http://oceanfile.com/webservices/"> <s:element name="StartWebServiceSession"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="AccountNumber" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="LoginName" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" /> </s:sequence> </s:complexType> </s:element> <s:element name="StartWebServiceSessionResponse"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="StartWebServiceSessionResult" type="tns:WebServiceResponse" /> </s:sequence> </s:complexType> </s:element> <s:complexType name="WebServiceResponse"> <s:sequence> <s:element minOccurs="1" maxOccurs="1" name="ResultCode" type="s:int" /> <s:element minOccurs="0" maxOccurs="1" name="ErrorMessage" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="ErrorTicketNumber" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="DataXml" type="s:string" /> </s:sequence> </s:complexType> <s:element name="InvokeMethod"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="TokenID" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="MethodName" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="Version" type="s:string" /> <s:element minOccurs="0" maxOccurs="1" name="RequestXML" type="s:string" /> </s:sequence> </s:complexType> </s:element> <s:element name="InvokeMethodResponse"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="InvokeMethodResult" type="tns:WebServiceResponse" /> </s:sequence> </s:complexType> </s:element> </s:schema> </wsdl:types> <wsdl:message name="StartWebServiceSessionSoapIn"> <wsdl:part name="parameters" element="tns:StartWebServiceSession" /> </wsdl:message> <wsdl:message name="StartWebServiceSessionSoapOut"> <wsdl:part name="parameters" element="tns:StartWebServiceSessionResponse" /> </wsdl:message> <wsdl:message name="InvokeMethodSoapIn"> <wsdl:part name="parameters" element="tns:InvokeMethod" /> </wsdl:message> <wsdl:message name="InvokeMethodSoapOut"> <wsdl:part name="parameters" element="tns:InvokeMethodResponse" /> </wsdl:message> <wsdl:portType name="WebServicesSoap"> <wsdl:operation name="StartWebServiceSession"> <wsdl:input message="tns:StartWebServiceSessionSoapIn" /> <wsdl:output message="tns:StartWebServiceSessionSoapOut" /> </wsdl:operation> <wsdl:operation name="InvokeMethod"> <wsdl:input message="tns:InvokeMethodSoapIn" /> <wsdl:output message="tns:InvokeMethodSoapOut" /> </wsdl:operation> </wsdl:portType> <wsdl:binding name="WebServicesSoap" type="tns:WebServicesSoap"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="StartWebServiceSession"> <soap:operation soapAction="http://oceanfile.com/webservices/StartWebServiceSession" style="document" /> <wsdl:input> <soap:body use="literal" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> <wsdl:operation name="InvokeMethod"> <soap:operation soapAction="http://oceanfile.com/webservices/InvokeMethod" style="document" /> <wsdl:input> <soap:body use="literal" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:binding name="WebServicesSoap12" type="tns:WebServicesSoap"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="StartWebServiceSession"> <soap12:operation soapAction="http://oceanfile.com/webservices/StartWebServiceSession" style="document" /> <wsdl:input> <soap12:body use="literal" /> </wsdl:input> <wsdl:output> <soap12:body use="literal" /> </wsdl:output> </wsdl:operation> <wsdl:operation name="InvokeMethod"> <soap12:operation soapAction="http://oceanfile.com/webservices/InvokeMethod" style="document" /> <wsdl:input> <soap12:body use="literal" /> </wsdl:input> <wsdl:output> <soap12:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="WebServices"> <wsdl:port name="WebServicesSoap" binding="tns:WebServicesSoap"> <soap:address location="http://www.oceanfile.com/rev4/wsv6/OceanfileServices.asmx" /> </wsdl:port> <wsdl:port name="WebServicesSoap12" binding="tns:WebServicesSoap12"> <soap12:address location="http://www.oceanfile.com/rev4/wsv6/OceanfileServices.asmx" /> </wsdl:port> </wsdl:service> </wsdl:definitions>
Thanks!
Neil
support-swapnaModeratorNeil,
Thank you for the wsdl. We are investigating the issue and we will get back to you soon.
Thanks for your patience.
support-swapnaModeratorNeil,
To enable SOAP 1.2 binding on an endpoint. You would need to set binding attribute value in sun-jaxws.xml to SOAP 1.2 HTTP binding value as specified by javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING which is: “http://www.w3.org/2003/05/soap/bindings/HTTP/” or “http://java.sun.com/xml/ns/jaxws/2003/05/soap/bindings/HTTP/”
I added the binding element and it fixes the deployment issue at my end.
Can you please replace the endpoint for “WebServicesSoap12” in the sun-jaxws.xml (/WEB-INF/sun-jaxws.xml) with the below code , deploy the project and see how it works ?
<endpoint name=”WebServicesSoap12″
implementation=”com.testws.WebServicesSoap12Impl”
binding=”http://java.sun.com/xml/ns/jaxws/2003/05/soap/bindings/HTTP/”
url-pattern=”/WebServicesSoap12″>
</endpoint>Let us know how it works for you.
neilrichardsParticipantHi Swapna,
Thanks for that. That got Tomcat starting up ok, however although the home page displays ok, I am getting a NullPointerException and am being referred to the .log file (below). Not too sure why that would be, looks like it may be another issue?
!SESSION 2015-02-06 11:04:17.988 ----------------------------------------------- eclipse.buildId=unknown java.version=1.7.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86_64 This is a continuation of log file C:\Users\richarn\Workspaces\MyEclipse 2015 CI\.metadata\.bak_0.log Created Time: 2015-02-06 16:25:06.648 !ENTRY org.eclipse.ui 4 0 2015-02-06 16:25:06.649 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Graphic is disposed at org.eclipse.swt.SWT.error(SWT.java:4441) at org.eclipse.swt.SWT.error(SWT.java:4356) at org.eclipse.swt.SWT.error(SWT.java:4327) at org.eclipse.swt.graphics.Image.getBounds(Image.java:1164) at net.jeeeyul.eclipse.themes.rendering.JeeeyulsTabRenderer.computeSize(JeeeyulsTabRenderer.java:155) at net.jeeeyul.eclipse.themes.rendering.JeeeyulsTabRenderer.computeSize(JeeeyulsTabRenderer.java:231) at org.eclipse.swt.custom.CTabFolder.updateTabHeight(CTabFolder.java:3718) at org.eclipse.swt.custom.CTabFolder.runUpdate(CTabFolder.java:3752) at org.eclipse.swt.custom.CTabItem.getBounds(CTabItem.java:149) at org.eclipse.swt.custom.CTabFolder.onPaint(CTabFolder.java:1993) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:289) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1070) at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:1491) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4667) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5036) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) 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:606) at com.genuitec.pulse.eclipse.launcher.Main.main(Main.java:110) !ENTRY org.eclipse.equinox.event 4 0 2015-02-06 16:25:19.352 !MESSAGE Exception while dispatching event org.osgi.service.event.Event [topic=org/eclipse/e4/ui/model/ui/ElementContainer/selectedElement/SET] to handler org.eclipse.e4.ui.services.internal.events.UIEventHandler@4b631562 !STACK 0 java.lang.NullPointerException at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.adjustTopRight(StackRenderer.java:759) at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1264) at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:68) at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4734) at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218) at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81) at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:488) at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:454) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:694) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:674) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:615) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:603) at org.eclipse.e4.ui.workbench.addons.dndaddon.DropAgent.reactivatePart(DropAgent.java:69) at org.eclipse.e4.ui.workbench.addons.dndaddon.StackDropAgent.reactivatePart(StackDropAgent.java:1) at org.eclipse.e4.ui.workbench.addons.dndaddon.StackDropAgent.drop(StackDropAgent.java:337) at org.eclipse.e4.ui.workbench.addons.dndaddon.DragAgent.dragFinished(DragAgent.java:159) at org.eclipse.e4.ui.workbench.addons.dndaddon.PartDragAgent.dragFinished(PartDragAgent.java:111) at org.eclipse.e4.ui.workbench.addons.dndaddon.DnDManager.finishDrag(DnDManager.java:276) at org.eclipse.e4.ui.workbench.addons.dndaddon.DnDManager.startDrag(DnDManager.java:243) at org.eclipse.e4.ui.workbench.addons.dndaddon.DnDManager$1.dragDetected(DnDManager.java:87) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:127) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) 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:606) at com.genuitec.pulse.eclipse.launcher.Main.main(Main.java:110)
Anyway, following this mini-tutorial:
https://www.genuitec.com/products/myeclipse/learning-center/ws/jax-ws-soap-web-services-overview/
I opened the Web Services Explorer but the Navigator link ‘WSDL Main’ will not expand – in the Actions section all it says is ‘IWAB0125E Select a node.’. I’ve attached a screen shot.
Any ideas?
Many thanks,
NeilAttachments:
You must be logged in to view attached files.
neilrichardsParticipant…. bizzare – having just sent the previous message I went back to the web services explorer and clicked the link again and it worked. Strange – but good news.
So I guess I’m ok now other than the npe – if you have any ideas 🙂
Thanks again,
Neil
neilrichardsParticipant…. as a follow-up, I seem to have to click the ‘refresh’ icon in the web services explorer every time I click a link in the navigator pane before the actions pane will refresh. I’m assuming that is not the intended behaviour?
Thanks again,
Neil
support-swapnaModeratorNeil,
The NPE you reported does not look like a Web Service issue.
Can you please replicate the error and let us know the exact steps you followed to help us replicate the issue at our end? Delete the contents of the .log file before replicating the issue. Please also send us the .log file.
I could replicate the issue with the refresh after clicking on the links in the Navigator pane. I raised a bug for the dev team to look into it. Thank you for pointing to it.
neilrichardsParticipantHI Swapna,
Sorry I can’t seem to replicate it now. Guess we’ll have to leave it :).
Thanks anyway!
Neil
support-swapnaModeratorNeil,
Glad that you are no longer seeing the issue.
Let us know if you see any issues. -
AuthorPosts