Ongoing discussion of Jetty problems in Eclipse with 2.6.1-rc2 (issue #8526)

2,684 views
Skip to first unread message

pron...@gmail.com

unread,
May 6, 2014, 2:23:42 PM5/6/14
to google-we...@googlegroups.com
This is a place where we can continue the discussion about issue #8526, rather than having a conversation within the bug report.


Summary so far: GWT 2.6.1-rc2 includes changes intended to fix issue #8526.  I've tested the changes, and they appear to work when I start dev mode on the command-line.  All of my Cucumber tests work in this situation, and I haven't seen anything broken when spot-checking by hand.  

However, when I try to start dev mode from Eclipse, using the standard Run As > Web Application provided by the Google Plugin for Eclipse, things are different. I get basically the same error I saw with GWT 2.6.0, prior to the recent fix (stack trace below).

I am working in Eclipse Kepler (build id 20130320-2352) using Google Plugin for Eclipse 3.5.1.v201312301723-rel-r43.  Although I use the Google Plugin for Eclipse, all of my dependencies come from Maven (via Gradle), and I do not rely on any bundled SDK provided by the Eclipse plugin.

I've tried a variety of different workarounds as documented in the bug report.  I've also tried a few other wild guesses not documented there, like starting over in a completely fresh workspace, changing JVMs (both 1.6 and 1.7), installing new bundled SDKs , moving the GWT jars to the top and bottom of the Eclipse classpath.  The result is the same no matter what I do.  

KEN

------

Starting Jetty on port 8888
   [WARN] Failed startup of context c.g.g.d.s.j.WebAppContextWithReload{/,file:/C:/Ken/Workspaces/GWT/SscTestSite/SscTestSite/war/},C:\Ken\Workspaces\GWT\SscTestSite\SscTestSite\war
java.lang.IllegalArgumentException: Object of class 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is not of type 'org.eclipse.jetty.webapp.WebAppContext'. Object Class and type Class are from different loaders.
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:323)
at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:281)
at org.eclipse.jetty.webapp.JettyWebXmlConfiguration.configure(JettyWebXmlConfiguration.java:103)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:468)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1237)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:541)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:162)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:740)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:522)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1104)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:844)
at com.google.gwt.dev.DevMode.main(DevMode.java:322)

Thomas Broyer

unread,
May 7, 2014, 5:06:20 AM5/7/14
to google-we...@googlegroups.com
It could be that you have the org.eclipse.jetty.webapp.WebAppContext class inside your webapp (somewhere in your WEB-INF).

pron...@gmail.com

unread,
May 7, 2014, 11:39:14 AM5/7/14
to google-we...@googlegroups.com
Yeah, that was it.  The gradle providedRuntime dependencies like gwt-dev were inadvertently getting copied into WEB-INF/lib.  As far as I can tell, it's been like that forever, but apparently didn't cause any problems with <= 2.5.1.  

The only oddity I'm left with is log4j initialization, but it looks like I can work around that with a bootstrap classpath entry as described here:


I think it's safe to say that issue #8526 is resolved.  I'll put a note in the issue tracker to that effect.

Thanks for all the help.

KEN

Kevin Wilson

unread,
Oct 2, 2015, 4:12:10 AM10/2/15
to GWT Users
Hello I have this problem when I try to start my local host (127.0.0.1) Could not find required bundle org.eclipse.jetty.webapp. Would you happen to know where I might download and install this missing bundle?

Kevin
Reply all
Reply to author
Forward
0 new messages