4 Replies Latest reply on Dec 29, 2010 9:14 PM by Ravi kiran Kuchika

    Rerender problem in a4j:commandlink

    Ravi kiran Kuchika Newbie

      Hi,

       

        I have a problem of rerendering the page using a4:commandLink.

       

      the problem is on click of the a4j:commanlLink am rerendering some data(may be huge) which is not rendering at all.

       

      Also am getting the "Stop running this javascript" for these type of scenarios.

       

      Is there any limit to display the content using Ajax response.

       

       

      Thanks

      Ravi Kuchika

        • 1. Re: Rerender problem in a4j:commandlink
          Ilya Shaikovsky Master

          It's really possible for old versions of IE for example if you reRendering huge parts of pages with rich components as all of them getting reinitialized during rendering. And that's not RF limitation. You just need to add some optimization to avoid massive rendering and JS executions via ajax. And make sure you using latest 3.3.3 Final version - many optimizations done there.

          • 2. Re: Rerender problem in a4j:commandlink
            Ravi kiran Kuchika Newbie

            Am using IE7. And 3.3.2 SR1 richfaces jars.

             

            "some optimization to avoid massive rendering and JS executions via ajax......"

             

            Can you explan the ways to optimize JS executions via ajax.

             

            My question is...is there any limitation for ajax response..meaning we can render this amount of data only?

             

             

             

             

             

            Thanks

            Ravi Kuchika

            • 3. Re: Rerender problem in a4j:commandlink
              Ilya Shaikovsky Master

              when you performing reRenedr of almost any Rich component next actions performed:

              • all the JS handlers getting detached from DOM for that component
              • component removed from DOM
              • new one inserted
              • initialization JavaScript called.

              So if you performing page updates for areas which contains too much rich components - browser just reports that because new components initialization JavaScript(last step) takes too long.

              • 4. Re: Rerender problem in a4j:commandlink
                Ravi kiran Kuchika Newbie

                So are you saying to change our design, so that too much of the rich components initialization can be avoided? but am using just a rich:datatable and inside that am using rich:columnGroup and rich:columns. But as u said our data is huge and the memory usage for this scenario its taking around 230MB and some around 50-55 CPU processes. Can you give me a solid solution apart from changing the design.

                 

                Thanks

                Ravi Kuchika