1. #1
    Sencha User
    Join Date
    Dec 2012
    Posts
    2
    Vote Rating
    0
    ramaraju256 is on a distinguished road

      0  

    Default Unanswered: Grid server-side paging is failed in web-mode

    Unanswered: Grid server-side paging is failed in web-mode


    Hi All,

    Gxt Version-->gxt-2.2.4-gwt22

    Grid server-side paging is failed in web-mode but it is working fine in dev-mode in web-mode it throws excepton

    SEVERE: data: An IncompatibleRemoteServiceException was thrown while processing this call.
    com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: java.lang.NoClassDefFoundError: com/google/gwt/core/client/GWTBridge
    at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:323)
    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:206)
    at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
    at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:877)
    at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:594)
    at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1675)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.google.gwt.user.client.rpc.SerializationException: java.lang.NoClassDefFoundError: com/google/gwt/core/client/GWTBridge
    at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java:691)
    at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readObject(ServerSerializationStreamReader.java:567)
    at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader$ValueReader$8.readValue(ServerSerializationStreamReader.java:140)
    at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeValue(ServerSerializationStreamReader.java:425)
    at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:312)
    ... 17 more

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Posts
    1,931
    Vote Rating
    55
    Answers
    73
    Colin Alworth is a jewel in the rough Colin Alworth is a jewel in the rough Colin Alworth is a jewel in the rough

      0  

    Default


    This exception is being thrown on the server - there isn't a difference in the server code when you are running in Dev Mode versus compiled Web Mode. So there is some other difference in how you are running in web mode than prod mode.

    From this part of your error message, it appears that you are using gwt-servlet.jar version 2.5.0 when running web mode, and either using a 2.4.0 version for dev mode, or adding other jars to the classpath when in dev mode.
    Code:
    java.lang.NoClassDefFoundError: com/google/gwt/core/client/GWTBridge
    A simple google search on this text brings up this bug report that affects only GWT 2.5.0: http://code.google.com/p/google-web-...detail?id=7527

    As discussed there, there are several fixes: Copy the GWTBridge class into your project, or add requestfactory-server.jar to your WEB-INF/lib/, or update to GWT trunk version, or back off to GWT 2.4.0.

  3. #3
    Ext GWT Premium Member
    Join Date
    Jul 2011
    Location
    Cluj-Napoca
    Posts
    67
    Vote Rating
    6
    lucaalex87 is on a distinguished road

      0  

    Default Solution

    Solution


    Hi,

    As Colin mentions, it's a defect in GWT 2.5 that google fixed, and will be released in 2.5.1.

    A quick fix is to add GWTBridge to your project. Add this in your project:

    Code:
    package com.google.gwt.core.client;
    import com.google.gwt.core.shared.*;
    /**
    * Date: 1/17/13
    * Time: 12:37 PM
    * This class is used for fixing class not found com.google.gwt.core.client.GWTBridge;
    *
    */
    public abstract class GWTBridge extends com.google.gwt.core.shared.GWTBridge {
    }
    If you want more details read here:

    http://alexluca.com/2013/01/17/gwt-2...ientgwtbridge/

    Regards,
    Alex.