- This topic has 6 replies, 2 voices, and was last updated 15 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
mongonvParticipantI am trying to go thru the “Developing JAX-WS Web Services & Clients with MyEclipse” tutorial and can create all the code based on the document, but when I try to “Run As/Debug As” as instructed the internal tomcat fails.
I am able to run it fine on the same computer using the MyEclipse 6.6 All-In-One install, but the 7.0 M2 fails with everything I try. I have tried using 1.5, 1.6, and MyEclipse built in JDK’s and including the libraries in the build. I am running on Windows XP and no changes to the computer were made between the 6.6 and 7.0 runs.
I created a new WorkSpace, left the Myeclipse JRE as the default VM and followed the steps in the tutorial. The steps worked in 6.6, but failed in 7.0, the console log is included below.
Any help would be greatly appreciated.
EdThe MyEclipse Web Browser gives a HTTP Status 404 – /WebServiceProject/
The Server console gives the following errors when the internal Tomcat is started:
Nov 25, 2008 7:32:47 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: E:\Program Files\MyEclipse 7.0 M2\bin;E:\Program Files\MyEclipse 7.0 M2\eclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_6.9.200.zmyeclipse69200200809\tomcat\bin
Nov 25, 2008 7:32:47 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 25, 2008 7:32:47 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 631 ms
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.13
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
java.lang.ClassNotFoundException: com.sun.xml.ws.transport.http.servlet.WSServletContextListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3770)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Nov 25, 2008 7:32:48 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/WebServiceProject] startup failed due to previous errors
Nov 25, 2008 7:32:49 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Nov 25, 2008 7:32:49 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Nov 25, 2008 7:32:49 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/31 config=null
Nov 25, 2008 7:32:49 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1179 ms
Riyad KallaMemberHrrm… let’s first reset your MyEclipse Tomcat install just incase…
Shut down Tomcat if it’s running, go to Window > Prefs > MyEclipse > Servers > Integrated Sandbox > Tomcat, and click the “Restore” button, now go back to your project (the web service one) and right-click, Run As or Debug as and select “MyEclipse Server Application” and choose MyEclipse Tomcat.
Did that work?
mongonvParticipantThanks for the reply.
I did those steps and the exact same issue happened. The restore had no impact on the problem.I did double check that the service of the local copy of tomcat is shut down. After doing the Debug As, the “MyEclipse Tomcat [default]” does show it is running and Mode is Debug, the application is listed under it and is shown as OK and Exploded.
Any other thoughts?
Ed
Riyad KallaMemberNext thing to is open Project properties, go to Java Build Path and libraries, and make sure that your JAX-WS libraries on the build path are in good shape. NOTE, you won’t be able to run a JAX-WS project with MyEclipse 6.6 in MyEclipse Tomcat, it has to be with MyEclipse 7.0M2, we specifically augmented the Tomcat install to include the Metro libraries so it would run out of the box that way. I think we even make a note of that in the tutorial.
Riyad KallaMemberEd,
Some more detailed steps for you to try is the following:
1. Drill back down to the Integrated Sandbox > Tomcat > JDK settings and make sure that the MyEclipse Tomcat server is setup to be launched with either the Java 5 JRE that we ship in MyEclipse or some other Java 5 or Java 6 (after 1.6.0_04) JRE or JDK on your system. If you’ve set it up with a Java 1.4 JRE/JDK, or a JRE/JDK before 1.6.0_04, that could explain the failure.
2. Make sure the JAX-WS library containers are in your project’s build path
3. After deploying your project (you can use the servers view or the deployment tool from the toolbar), open a file manager and drill down to that deployment dir and check the WEB-INF/lib directory to make sure the JAX-WS libraries got deployed for sure with the project.
mongonvParticipantThanks for the reply Riyad,
It was the JAX-WS libs on the project class path. Doing Debug AS now runs and brings up the page created in the tutorial.Appreciate the help with a DUHHH mistake on my part.
Riyad KallaMemberNo worries, glad it’s working.
-
AuthorPosts