Jetspeed 2.1.3/tomcat5.5.27
I've run into an interesting issue. I have a portlet that contains a
tomahawk datatable of links. When a user clicks on one of the links the
browser opens a new window, with an address of javascript:void(0), this
is in turn interpreted as /http://myhost/myportal/undefined/ and waits
to catch the response from the portlet response.
The portlet's ( who's portlet class is
org.apache.portals.bridges.jsf.FacesPortlet ) process action is run in
turn calling our own code, which does some lookups in our database, and
does a single sign on to a third party.
We do an insert in their database, create a url and redirect the
ActionResponse to the created url wich is returned to the targetted popup.
Most of the time everything works as expected but occasionally the popup
window ends up returning the same page as the original (the
default-page.psml for the user). There are no errors or exceptions being
thrown.
My suspision is that the portlet response is timing out before the
redirect occurs. In an effort to test this theory I've been trying to
reset the timeout on the portlet as described here:
http://portals.apache.org/jetspeed-2/deployguide/guide-aggregation.html
I've tried resetting the timeout value in the jetspeed-portlets.xml to 1
millisecond to force the portal to timeout, however the portlet still
renders and the popup link behaviour remains the same, mostly working
but failing occasionally. Tomcat is restarted when I change the timeout
value.
Once it has failed once, it seems to repeat the same behavior until a
shift+refresh in the browser. After several failures the
PortletTrackingManager deactivates the portlet and writes its message to
the page.
Another page refresh returns the portlet.
At one millisecond, shouldn't the portlet fail everytime?
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
