Announcement

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

    Warning: Attempted to call getRecord() on a DSResponse with null DataSource

    Using SGWT 3.0 release, we get this warning often, I have read this thread below but it did not help much because we don't have access to the response.

    http://forums.smartclient.com/showthread.php?t=20999

    As the stack trace shows it, our code calls
    IDACall.processRPCTransaction(RPCManager, RequestContext)

    And so the DSResponse is not under our control, I have looked at the request in the RPCManager and it has a DataSource.
    So what can we do to get rid of this warning?

    Thanks,

    Gael

    Code:
    Logger.warn(Object) line: 364	
    DSResponse.getRecords() line: 992	
    RPCManager.encodeBinaryStreams() line: 1528	
    RPCManager.completeResponse() line: 1075	
    RPCManager.send(DSRequest, DSResponse) line: 582	
    ApplicationServiceServlet(IDACall).processRPCTransaction(RPCManager, RequestContext) line: 156	
    ApplicationServiceServlet.processRPCTransaction(RPCManager, RequestContext) line: 88	
    ApplicationServiceServlet(IDACall).processRequest(HttpServletRequest, HttpServletResponse) line: 121	
    ApplicationServiceServlet(IDACall).doPost(HttpServletRequest, HttpServletResponse) line: 73

    #2
    As the other thread indicates, you need to add a DataSource to DSResponses you generate. All automatically generated DSResponses already include DataSources. If you disagree, please show a minimal, standalone test case that allows the warning to be reproduced.

    Comment


      #3
      Thanks for your reply.
      As I said above, the response is automatically generated by SGWT.
      So, I'd be glad to provide you with a minimal test case, could you just point me to a server-side sample that I could use as a starting point?

      Thanks

      Comment


        #4
        Make sure you are using a fully patched build (see SmartClient.com/builds), then, if the problem is still happening, pick any sample where you think you can reproduce it, and show minimal modifications to that sample that cause the problem.

        Comment

        Working...
        X