Announcement

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

    Custom Widget with multiple data bindings

    Here is my use case:

    Provide a Google Earth Map interface, and render certain pieces of data on that map.

    This data ultimately resides in 3 different tables.

    So I have the following code snippets

    Once the google earth plugin has initialized I then attempt to call the following code



    Which ultimately is this


    Here is where things get interesting. So I deploy my application and open the map. I see the plugin initialize, a dialog about fetching data from server. And things just don't seem to finish. So I go looking at the dev console and I find no errors. Firebug has no errors. The RPC watch shows that only the first fetch has executed, and has returned successfully. And the server log is clean, no errors.

    So I try to debug in hosted mode, something must be going wrong, and sometimes the only way to find errors is in hosted mode. Well in hosted mode, it works. All 3 fetches are performed and I see all of the data on the map as expected.

    Any ideas what is going wrong when compiled to js?
    Last edited by jpappalardo; 24 Sep 2014, 09:36.

    #2
    Generally if there's a difference in behavior it's a core GWT (not SmartGWT bug).

    Can you clarify, do you see the other two fetches *never happen at all*, or do they happen and are successfully processed by the server but the resulting logic on the client never happens (the RPC call is shown as not completed)?

    Comment


      #3
      Should also mention - you could have a logic bug in your code being exposed by the different execution speed of compiled mode.

      Comment


        #4
        I never see the last two fetches occur at all.

        If I set it up such that I only request one fetch, and then in the DataArrivedHandler, process the response, and request the next fetch. I can successfully get all 3 fetches to occur however the connecting to server dialog never disappears after the third fetch completes.

        Comment


          #5
          Without a test case pointing to a framework issue, and with no reports of similar problems, there's not much we can do to help yet. It does sound like either a timing problem or GWT bug, the former being more likely than the latter.

          As far as the third request not completing once you've reordered them, you haven't mentioned any of the usual data we'd ask for: what's in the RPC tab, was there a server error, etc.

          Comment


            #6
            Here is a test case I put together using the jpa ds sample

            In hosted mode all works as expected, well except that datachanged gets called twice. I didn't expect that.

            2 fetches occur.

            Running deployed it does not work as expected.

            1 fetch occurs

            There are no errors in the server, in the dev console, in firebug, anywhere.
            The second fetch doesnt even begin to happen.
            Last edited by jpappalardo; 24 Sep 2014, 09:36.

            Comment


              #7
              In an attempt to try and figure out what is going wrong I modified my code as so

              This leads to having all fetches complete as expected and data rendered. Perhaps this will help to nail down where things are going wrong?
              Last edited by jpappalardo; 24 Sep 2014, 09:37.

              Comment


                #8
                You're reporting a lot of very weird and contradictory stuff here and it's probably time to try any other developer's environment, as you may just have somehow corrupted yours.

                Comment


                  #9
                  What is contradictory? That I'm catching exceptions from causing ResultSets to fetch? I dont understand

                  Comment


                    #10
                    That refactoring your real application code to do parallel ResultSet fetches works while a simple test case doing the same thing doesn't.

                    But what is also contradictory is having a super simple sample of parallel fetches just not work at all in deployed mode. If that were to fail, everything in your app should fail, not just one particular codepath.

                    Comment


                      #11
                      Does my test case work for you?

                      Comment


                        #12
                        We don't have any of your versions or your deployment environment, so we haven't tried to replicate your findings.

                        Comment


                          #13
                          Just to clarify that - every single time a developer checks in a suite of around 2500 (and growing) tests is run. Several hundred involve concurrent fetches and would be breaking if the framework were broken in a general way here. Hence there's no point in our trying to replicate this without finding out what's special about your environment.

                          Comment


                            #14
                            SmartClient Version: v8.2p_2012-04-18/PowerEdition Deployment (built 2012-04-18)

                            Comment


                              #15
                              I dont see how my environment could be particularly special.

                              SmartClient Version: v8.2p_2012-04-18/PowerEdition Deployment (built 2012-04-18)

                              Deploying to JBoss 7.1.0 Final

                              Comment

                              Working...
                              X