JSR 168 Portlet and PORTLET_SCOPE session variables

Question

Hi,
I have a JSR-168 portlet that is putting session variables on the PortletSession. I have some variables that use "PORTLET_SCOPE" for that particular portlet. This works fine if I add the portlet directly on a page, no problems. Its able to retrieve and put variables on the PortletSession with PORTLET_SCOPE and retrieve them properly.
The problem comes when when I have my JSR-168 portlet on a page, then select "Publish Page as Portlet", and then add that page (that contains the JSR-168 Portlet) to another page. Now, when I try to retrieve a variable that was put on the PortletSession w/ PORTLET_SCOPE, it returns null. So its like variables put on the PortletSession with PORTLET_SCOPE doesn't work properly if you add it as a page onto another page.
In case that wasn't clear, let's say I have Page1 which contains my JSR-168 portlet and I selected "Publish Page as a Portlet."
If I go to Page1, it works fine, no problems at all.
Now, I have Page 2. I add Page 1 to Page 2. NOW, the Portlet on Page 1 doesn't work properly and I've narrowed it down to a problem with the PortletSession when PORTLET_SCOPE is used. Has anyone else run into this problem? I'm guessing the problem is the fact that page is published as a portlet and PORTLET_SCOPE doesn't work properly. Is this a bug or expected behavior?? If so, is there a workaround?
Thanks in advance.

Answer 1

Frank,
The taglib is not in the classpath of the Portal server. We access other methods of the ftl taglib, like <f:webResources relativePath='js/myScripts.js' />at places higher up in the JSP and it has no problems with those ftl taglib calls.
If I understand correctly, since the Portal is hosting a remote portlet, the Portal is only getting html from the remote portlet producer, not the actual JSP to compile into a web page. If that is true, the Portal never sees the taglib code, just the html that is produced from it - so it would not need the taglib in its classpath.
There is something special about the "invoke" method of the taglib where it makes a call back to the Enterprise server. I think when it tries to go back to the Enterprise server, the Portal server has a problem with it.
Thanks.
Edited by marshallbenfield at 08/15/2007 6:02 AM
Edited by marshallbenfield at 08/15/2007 6:03 AM