Scott,
Your mentioned solution of copying gwt-servlet.jar into WEB-INF/lib
did work for the webAppCreator project, however my existing large
project still has the ClassNotFoundException for
org.apache.xerces.jaxp.SAXParserFactoryImpl. I am still at a loss of
ideas, as gwt-user.jar, gwt-dev-windows.jar, and gwt-servlet.jar are
the same with both projects. Could it be possible another server-side
lib is causing a conflict? The complete stack trace is below:
2009-02-15 23:01:30.086::WARN: failed
com.google.gwt.dev.shell.jetty.JettyLauncher
$webappcontextwithrel...@c8ba50{/,E:\project_src\ProjGWT\war}
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found
at javax.xml.parsers.SAXParserFactory.newInstance
(SAXParserFactory.java:134)
at org.mortbay.xml.XmlParser.setValidating(XmlParser.java:92)
at org.mortbay.xml.XmlParser.<init>(XmlParser.java:84)
at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp
(TagLibConfiguration.java:199)
at org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1217)
at org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:513)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
448)
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload.doStart(JettyLauncher.java:236)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start
(JettyLauncher.java:283)
at com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:368)
at com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:587)
at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:394)
at com.google.gwt.dev.HostedMode.main(HostedMode.java:231)
2009-02-15 23:01:30.086::WARN: Nested in
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found:
java.lang.ClassNotFoundException
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload$1.findClass(JettyLauncher.java:217)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
(WebAppClassLoader.java:375)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
(WebAppClassLoader.java:337)
at javax.xml.parsers.FactoryFinder.getProviderClass
(FactoryFinder.java:111)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:
146)
at javax.xml.parsers.FactoryFinder.findJarServiceProvider
(FactoryFinder.java:298)
at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:223)
at javax.xml.parsers.SAXParserFactory.newInstance
(SAXParserFactory.java:128)
at org.mortbay.xml.XmlParser.setValidating(XmlParser.java:92)
at org.mortbay.xml.XmlParser.<init>(XmlParser.java:84)
at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp
(TagLibConfiguration.java:199)
at org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1217)
at org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:513)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
448)
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload.doStart(JettyLauncher.java:236)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start
(JettyLauncher.java:283)
at com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:368)
at com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:587)
at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:394)
at com.google.gwt.dev.HostedMode.main(HostedMode.java:231)
2009-02-15 23:01:30.086::WARN: Error starting handlers
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found
at javax.xml.parsers.SAXParserFactory.newInstance
(SAXParserFactory.java:134)
at org.mortbay.xml.XmlParser.setValidating(XmlParser.java:92)
at org.mortbay.xml.XmlParser.<init>(XmlParser.java:84)
at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp
(TagLibConfiguration.java:199)
at org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1217)
at org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:513)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
448)
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload.doStart(JettyLauncher.java:236)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start
(JettyLauncher.java:283)
at com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:368)
at com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:587)
at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:394)
at com.google.gwt.dev.HostedMode.main(HostedMode.java:231)
2009-02-15 23:01:30.086::WARN: Nested in
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found:
java.lang.ClassNotFoundException
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload$1.findClass(JettyLauncher.java:217)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
(WebAppClassLoader.java:375)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass
(WebAppClassLoader.java:337)
at javax.xml.parsers.FactoryFinder.getProviderClass
(FactoryFinder.java:111)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:
146)
at javax.xml.parsers.FactoryFinder.findJarServiceProvider
(FactoryFinder.java:298)
at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:223)
at javax.xml.parsers.SAXParserFactory.newInstance
(SAXParserFactory.java:128)
at org.mortbay.xml.XmlParser.setValidating(XmlParser.java:92)
at org.mortbay.xml.XmlParser.<init>(XmlParser.java:84)
at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp
(TagLibConfiguration.java:199)
at org.mortbay.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1217)
at org.mortbay.jetty.handler.ContextHandler.doStart
(ContextHandler.java:513)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
448)
at com.google.gwt.dev.shell.jetty.JettyLauncher
$WebAppContextWithReload.doStart(JettyLauncher.java:236)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart
(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at com.google.gwt.dev.shell.jetty.JettyLauncher.start
(JettyLauncher.java:283)
at com.google.gwt.dev.HostedMode.doStartUpServer(HostedMode.java:368)
at com.google.gwt.dev.HostedModeBase.startUp(HostedModeBase.java:587)
at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:394)
at com.google.gwt.dev.HostedMode.main(HostedMode.java:231)
On Feb 13, 2:18 pm, Scott Blum <sco...@google.com> wrote:
> Not sure what might be causing the SAX problem. Can you file an issue with
> more detailed information?
> The NoClassDefFound is caused by not copying gwt-servlet.jar into
> WEB-INF/lib. If you run the ant build file, it will do this automatically,
> but we have a fix in place for the next milestone that makes webAppCreator
> go ahead and do this for you for the case where you're just loading the
> project up in Eclipse without ever running the build file.
>
> This particular error state is now detailed here in the "common pitfalls"
> section:http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6&s=goog...
>
> On Fri, Feb 13, 2009 at 2:25 PM, Jeff J. <jsjenkins...@gmail.com> wrote:
>
> > I'm getting class not found exceptions when trying to launch my
> > project in hosted mode using this build, saying Provider
> > org.apache.xerces.jaxp.SAXParserFactoryImpl not found. I tried to
> > create a fresh new project using webAppCreator and I get
> > NoClassDefFoundError looking for com/google/gwt/user/client/rpc/
> > RemoteService. I'm using jdk1.6.0_11 32bit JVM on windowsXP 64bit. Any
> > suggestions on what I could be doing wrong? For now I am needing to
> > use r4603 from the trunk with the modified jetty jar in the gwt tools
> > to use hosted mode.
>
> > Thanks,
> > Jeff
>
> > On Feb 6, 3:22 pm, Scott Blum <sco...@google.com> wrote:
> > > On Fri, Feb 6, 2009 at 12:30 PM, Matthew Mastracci <
> > matt...@mastracci.com>wrote:
>
> > > > 2. The compiler task crashes Java 1.6 on Mac now. The previous
> > versions
> > > > would run fine with the 64-bit JVM (even though SWT isn't compatible).
> > > > Would it be possible to lazy load SWT so that we can take advantage of
> > the
> > > > faster 1.6 JVM on OSX?
>
> > > > [java] Invalid memory access of location 00000000 rip=01160767
>
> > > Good point, I can take a look at this. The compiler should be able to
> > run
> > > without loading SWT.
>
> > > 5. One cool thing that was missing from the release notes is new the
>
> > > > ability to specify multiple modules for the compile task. Based on
> > some
> > > > wallclock testing, specifying multiple modules shaves off ~30 seconds
> > off
> > > > compile time of any modules on top of the first:
>
> > > > Individual times:
>
> > > > [java] Compilation succeeded -- 51.814s
> > > > [java] Compilation succeeded -- 170.986s
> > > > [java] Compilation succeeded -- 91.488s
>
> > > > All together:
>
> > > > [java] Compilation succeeded -- 55.121s
> > > > [java] Compilation succeeded -- 141.052s
> > > > [java] Compilation succeeded -- 55.492s
>
> > > > Note that each module's log messages are indented one level further,
> > > > indicating the extra speed boost. ;)
>
> > > LOL! I had no idea this actually made any difference in speed, so I
> > guess
> > > it's a bonus easter egg feature. :P
>
> > > Scott
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
