Topic
  • 1 reply
  • Latest Post - ‏2013-07-10T20:33:03Z by mburati
santhiramya
santhiramya
14 Posts

Pinned topic Page refreshing twice every time data is submitted from tree hirearchy portlet to second portlet

‏2013-07-10T06:29:34Z |

Hi,

i have a scenario where the page reloads twice when ever data is submitted from tree hierarchy portlet to target portlet which are on the same page.

how can i avoid this second time refreshing of the page.

im using tree builder for tree hierarchy in the portlet.when i select any child item ,the target portlet has to show up giving details of this child item.this is what we are doing.For moving data from one portlet to target portlet we are firing both client side and server side events.

As per the sample from WEFsamples we are following the same way for achieving the above.(http://www-10.lotus.com/ldd/pfwiki.nsf/dx/Web_Expereince_Factory_Samples_Categorized).

thus as already said here is where the page reloads twice when data is shared from source portlet to target portlet.

plz suggest me how i can get solution for this reloading problem....

 

Thanks in advance..........

Regards

Shanthi.

 

 

 

 

  • mburati
    mburati
    2568 Posts

    Re: Page refreshing twice every time data is submitted from tree hirearchy portlet to second portlet

    ‏2013-07-10T20:33:03Z  

    Does the sample you refer to also exhibit that (double-refresh) behavior or just your use of the technique from that article?

    There are (at least) two reasons I can think of for such a double-page-refresh:

    (1)  Both portlets are being hit with URLs that trigger a portal page refresh

    (2) One (or both) portlets execute a Partial Page / Smart Refresh AJAX based URL which does NOT receive the page HTML it was expecting (the id of the html element its looking for is not in the response) and thus the PPR/SmartRefresh code does a full page refresh in case it's due to a session/authentication timeout (which can help you get back to the portal login page) or another transient error that a full page refresh may resolve.

    If it's the latter (unexpected result) cause then running it with the browser console open (Firebug or Chrome Debugger or IE Dev Tools) can often tell you if there's a Javascript error or unexpected response error coming back from one of the AJAX requests).

    I hope that info helps,
    ..Mike Burati 
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.