Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Null on DSRequest.buildIncludeFromDefinitions since 2.4

    I just upgraded from 2.3 to 2.4 And I got this error:

    It is on the trial version, we are in the process to purchase the power version.

    It is on a complex fetch that use custom sql and velocity templating. But it worked with 2.3.

    Other datasource seem to work well, even those with custom sql fetch (but simpler).

    Anyone have idea where it is coming from?

    System.out:
    Code:
    === 2011-01-11 10:22:16,760 [0-11] DEBUG RPCManager - Request #1 (DSRequest) payload: {
        criteria:{
            cl_telephone_operator:"contient",
            cl_telephone:"819840242",
            login_alias_operator:"contient",
            statut_login_alias:"actif",
            statut_equipement:"actif",
            __gwt_ObjectId:2632
        },
        operationConfig:{
            dataSource:"recherche",
            operationType:"fetch",
            textMatchStyle:"exact"
        },
        componentId:"isc_ListGrid_0",
        appID:"builtinApplication",
        operation:"recherche_fetch",
        oldValues:{
            cl_telephone_operator:"contient",
            cl_telephone:"819840242",
            login_alias_operator:"contient",
            statut_login_alias:"actif",
            statut_equipement:"actif",
            __gwt_ObjectId:2632
        }
    }
    === 2011-01-11 10:22:16,760 [0-11] INFO  IDACall - Performing 1 operation(s)
    === 2011-01-11 10:22:16,760 [0-11] WARN  RequestContext - dsRequest.execute() failed:
    java.lang.NullPointerException
     at com.isomorphic.datasource.DSRequest.buildIncludeFromDefinitions(DSRequest.java:2983)
     at com.isomorphic.datasource.DSRequest.execute(DSRequest.java:1348)
     at com.isomorphic.servlet.IDACall.handleDSRequest(IDACall.java:173)
     at com.isomorphic.servlet.IDACall.processRPCTransaction(IDACall.java:130)
     at com.isomorphic.servlet.IDACall.processRequest(IDACall.java:95)
     at com.isomorphic.servlet.IDACall.doPost(IDACall.java:54)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
     at com.isomorphic.servlet.BaseServlet.service(BaseServlet.java:152)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
     at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
     at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
     at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
     at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
     at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
     at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
     at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
     at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
     at org.mortbay.jetty.Server.handle(Server.java:324)
     at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
     at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:843)
     at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647)
     at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
     at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
     at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
     at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)
    DSRequest:
    Code:
    {
        "actionURL":"http://127.0.0.1:8888/csmpapp/sc/IDACall", 
        "showPrompt":true, 
        "prompt":"Recherche des enregistrements correspondant à vos critères...", 
        "transport":"xmlHttpRequest", 
        "promptStyle":"cursor", 
        "bypassCache":true, 
        "data":{
            "criteria":{
                "cl_telephone_operator":"contient", 
                "cl_telephone":"819840242", 
                "login_alias_operator":"contient", 
                "statut_login_alias":"actif", 
                "statut_equipement":"actif"
            }, 
            "operationConfig":{
                "dataSource":"recherche", 
                "repo":null, 
                "operationType":"fetch", 
                "textMatchStyle":"exact"
            }, 
            "componentId":"isc_ListGrid_0", 
            "appID":"builtinApplication", 
            "operation":"recherche_fetch", 
            "oldValues":{
                "cl_telephone_operator":"contient", 
                "cl_telephone":"819840242", 
                "login_alias_operator":"contient", 
                "statut_login_alias":"actif", 
                "statut_equipement":"actif"
            }
        }
    }
    DSResponse:
    Code:
    [
        {
            queueStatus:-1, 
            isDSResponse:true, 
            invalidateCache:false, 
            status:-1, 
            data:null
        }
    ]
    Last edited by jgauthier; 11 Jan 2011, 11:26.

    #2
    Please post the .ds.xml files involved (if one DataSource inheritsFrom another, post all involved).

    Comment


      #3
      Here it is
      Attached Files

      Comment


        #4
        This is happening because the criteria you pass to the server contains field names that do not refer to fields on the DataSource. This is a bug in the server, which we've now fixed.

        Comment


          #5
          ok, but these:
          Code:
                  cl_telephone_operator:"contient",
                  cl_telephone:"819840242",
                  login_alias_operator:"contient",
                  statut_login_alias:"actif",
                  statut_equipement:"actif",
                  __gwt_ObjectId:2632
          Are all in the DS except the __gwt_ObjectId.

          But some are hidden or/and excluded in the output or in excludeCriteriaFields.

          How can we get your fix? They are a nightly build for the EE trial version?

          Comment


            #6
            The _gwt_ObjectId property that's causing the problem will only appear in Chrome in Hosted/Development mode and is due to a core GWT bug. See the FAQ on this.

            Comment

            Working...
            X