Announcement Announcement Module
Collapse
No announcement yet.
STS 2.8, Roo 1.2M1, GWT jetty problem? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS 2.8, Roo 1.2M1, GWT jetty problem?

    After Roo generates everything the only warning in .server or .shared is:
    The serializable class CustomRequestFactoryServlet does not declare a static final serialVersionUID field of type long
    I've tried it with and without a serialVersionUID, so I don't think that's it.

    Is the generated web.xml correct or is there some other problem?
    Code:
        <servlet>
            <servlet-name>requestFactory</servlet-name>
            <servlet-class>com.brockgroup.server.CustomRequestFactoryServlet</servlet-class>
        </servlet>
        <servlet-mapping>
            <servlet-name>mims_gwt</servlet-name>
            <url-pattern>/</url-pattern>
        </servlet-mapping>
        <servlet-mapping>
            <servlet-name>requestFactory</servlet-name>
            <url-pattern>/gwtRequest</url-pattern>
        </servlet-mapping>
    Here's what happens when I try to run as Web Application:
    Starting Jetty on port 8888
    [WARN] EXCEPTION
    java.lang.ClassNotFoundException: com.brockgroup.server.CustomRequestFactoryServlet
    at java.lang.ClassLoader.findClass(ClassLoader.java:5 22)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:4 23)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:3 56)
    at org.mortbay.jetty.webapp.WebAppClassLoader.loadCla ss(WebAppClassLoader.java:352)
    at org.mortbay.jetty.webapp.WebAppClassLoader.loadCla ss(WebAppClassLoader.java:337)
    at org.mortbay.util.Loader.loadClass(Loader.java:91)
    at org.mortbay.util.Loader.loadClass(Loader.java:71)
    at org.mortbay.jetty.servlet.Holder.doStart(Holder.ja va:73)
    at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:233)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.java:616)
    at org.mortbay.jetty.servlet.Context.startContext(Con text.java:140)
    at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1220)
    at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:513)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:448)
    at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAp pContextWithReload.doStart(JettyLauncher.java:468)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.handler.RequestLogHandler.doStar t(RequestLogHandler.java:115)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.Server.doStart(Server.java:222)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at com.google.gwt.dev.shell.jetty.JettyLauncher.start (JettyLauncher.java:672)
    at com.google.gwt.dev.DevMode.doStartUpServer(DevMode .java:509)
    at com.google.gwt.dev.DevModeBase.startUp(DevModeBase .java:1068)
    at com.google.gwt.dev.DevModeBase.run(DevModeBase.jav a:811)
    at com.google.gwt.dev.DevMode.main(DevMode.java:311)
    [WARN] failed requestFactory
    javax.servlet.UnavailableException: com.brockgroup.server.CustomRequestFactoryServlet
    at org.mortbay.jetty.servlet.Holder.doStart(Holder.ja va:79)
    at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:233)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.java:616)
    at org.mortbay.jetty.servlet.Context.startContext(Con text.java:140)
    at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1220)
    at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:513)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:448)
    at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAp pContextWithReload.doStart(JettyLauncher.java:468)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.handler.RequestLogHandler.doStar t(RequestLogHandler.java:115)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.Server.doStart(Server.java:222)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at com.google.gwt.dev.shell.jetty.JettyLauncher.start (JettyLauncher.java:672)
    at com.google.gwt.dev.DevMode.doStartUpServer(DevMode .java:509)
    at com.google.gwt.dev.DevModeBase.startUp(DevModeBase .java:1068)
    at com.google.gwt.dev.DevModeBase.run(DevModeBase.jav a:811)
    at com.google.gwt.dev.DevMode.main(DevMode.java:311)
    [WARN] Failed startup of context com.google.gwt.dev.shell.jetty.JettyLauncher$WebAp pContextWithReload@1164661{/,C:\Users\justin.c\Documents\workspace-sts roo 1.2\mims_gwt\target\mims_gwt-0.1.0.BUILD-SNAPSHOT}
    javax.servlet.UnavailableException: com.brockgroup.server.CustomRequestFactoryServlet
    at org.mortbay.jetty.servlet.Holder.doStart(Holder.ja va:79)
    at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:233)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.java:616)
    at org.mortbay.jetty.servlet.Context.startContext(Con text.java:140)
    at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1220)
    at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:513)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:448)
    at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAp pContextWithReload.doStart(JettyLauncher.java:468)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.handler.RequestLogHandler.doStar t(RequestLogHandler.java:115)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.Server.doStart(Server.java:222)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:39)
    at com.google.gwt.dev.shell.jetty.JettyLauncher.start (JettyLauncher.java:672)
    at com.google.gwt.dev.DevMode.doStartUpServer(DevMode .java:509)
    at com.google.gwt.dev.DevModeBase.startUp(DevModeBase .java:1068)
    at com.google.gwt.dev.DevModeBase.run(DevModeBase.jav a:811)
    at com.google.gwt.dev.DevMode.main(DevMode.java:311)

  • #2
    I think the problem is in the pom, but I have no clue how to solve it. I get a command execution failed error. The default quick fix is to ignore, but it can't be ignored and executing results in a maven error. How can I get details on how or why it failed?

    Code:
            <plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>exec-maven-plugin</artifactId>
                    <version>1.2</version>
                    <executions>
                        <execution>
                            <phase>process-classes</phase>
                            <goals>
                                <goal>exec</goal>
                            </goals>
                            <configuration>
                                <id>VerifyRequestFactoryInterfaces</id>
                                <executable>java</executable>
                                <arguments>
                                    <argument>-cp</argument>
                                    <classpath/>
                                    <argument>com.google.web.bindery.requestfactory.apt.ValidationTool</argument>
                                    <argument>${project.build.outputDirectory}</argument>
                                    <argument>${project.groupId}.client.managed.request.ApplicationRequestFactory</argument>
                                </arguments>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>

    Comment


    • #3
      Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:exec-maven

      Same problem here, I got the message

      Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:exec-maven-plugin:1.2:exec (execution: default, phase: process-classes) pom.xml /pasarela line 579 Maven Project Build Lifecycle Mapping Problem
      I googled it and it seems to be like it need to specify a lifecycle-mapping, but I haven't found how to do this properly.

      I found this post:
      http://stackoverflow.com/questions/6...tion-for-sprin

      That seems is quite similar to what I think would solve the problem, but I don't know what to do with the arguments...

      David

      Comment


      • #4
        Hi Justin,

        I believe you posted the same question in a different thread. Anyway, I post here a link to the solution in case somebody else is looking for it:

        http://forum.springsource.org/showth...ht=#post385963

        Comment

        Working...
        X