|
Home > Archive > WebSphere Portal Server > March 2007 > jsf jsr 168 portlet -- issue with portlet rendering
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
jsf jsr 168 portlet -- issue with portlet rendering
|
|
|
| Our env - IBM WebSphere Portal 5.1.0.2
I have an issue with a custom designed JSF jsr 168 portlet. I am trying to make the portlet not remember its state on subsequent requests to the portlet(if the link is not internal to the portlet). I have it working for a simple jsf portlet, but when I t
ried to port the same logic to our other portlets its losing the state in middle of normal interaction with portlet.
After tracing the flow of portlet It looks like for some portlet instances, the render method of the portlet is called twice(which calls doView twice). The second time it looses all the parameters passed through the portlet (and processAction). This is ca
using the portlet to not remember its state. I am not able to replicate this double rendering locally on my laptop portal instance. I have checked all my web-artifacts (.js, images) and there are no broken links on the portal page where the portlet is ren
dered twice.
The surprising part is this double rendering of the portlet is not occuring on all portlet clones. I would appreciate if anyone has faced similar issue and have any suggestions regarding this.
| |
| bn_shyam 2007-03-22, 7:26 pm |
| Hey,
Were you able to figure out why this was happening?
Shyam
|
|
|
|
|