Portal 6.1 JSF Portlet - action automatically triggered in renderphase - Websphere

This is a discussion on Portal 6.1 JSF Portlet - action automatically triggered in renderphase - Websphere ; I developed a JSF Portlet project using JSR286 API and deployed on IBM WebSphere Portal, Version 6.1.0.0 Basically Portlet is developed for showing report. Implemented Approach – When user click on report link, a request is send to server, to ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Portal 6.1 JSF Portlet - action automatically triggered in renderphase

  1. Portal 6.1 JSF Portlet - action automatically triggered in renderphase

    I developed a JSF Portlet project using JSR286 API and deployed on IBM WebSphere Portal, Version 6.1.0.0

    Basically Portlet is developed for showing report.

    Implemented Approach – When user click on report link, a request is send to server, to retrieve a report url, then jsp is rendered. In the same jsp page there is block, that check whether report url is generated or not. If report_url is in the request scope then a javascript code is rendered on webpage which send a request to portlet to serve the cognos report in a new window. This will happen on a single click & second request is sent by browser automatically though javascript.


    So once user generates a report and next time when the user clicks on refresh or click on other portlet on the same page, then the somehow action is getting triggered on this portlet and generates a report even though user explicitly hasn't initiated it.


    If anybody experience this kind of issue, please provide a solution.

  2. Re: Portal 6.1 JSF Portlet - action automatically triggered inrender phase

    Use h:commandLink instead of hx:commandExButton Ex-





    function removeReadyReport(eventHandle) {
    ans=confirm('alert_remove');
    if(ans==false) {
    // pop event bubble
    if (!eventHandle)
    var eventHandle = window.event;
    if (eventHandle)
    eventHandle.cancelBubble = true;
    if (eventHandle.stopPropagation)
    eventHandle.stopPropagation();
    }
    return true;
    }

+ Reply to Thread