With reference to my previous post:
The AJAX request issue is resolved after enabling the session for anonymous pages, but after doing so Portal seems to cache the portlet results - Actually the model in model container gets switched based on the query string parameter, example:
were returning different results, but after turning public.session=true the URL which I hit later on returns the same result as first one.
This topic has been locked.
2 replies Latest Post - 2012-11-28T09:37:24Z by TahaSaghir
Pinned topic Having caching issue after enabling session for anonymous page
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-28T09:37:24Z at 2012-11-28T09:37:24Z by TahaSaghir
mburati 060000VQ202544 PostsACCEPTED ANSWER
Re: Having caching issue after enabling session for anonymous page2012-11-26T22:03:38Z in response to TahaSaghirBefore you enabled that, you were likely getting and populating a new session every request, so it was probably reinitializing the webapp each time. Afterwards, the model/webapp has already been regenerated and it's using what's there when you ask portal to re-render the page. How/where/when are you looking for a request parameter to the portal page to determine which model to contain? That does not seem like a typical use case (vs some action in the page changing the contained model).
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
TahaSaghir 270004DUU77 PostsACCEPTED ANSWER
Re: Having caching issue after enabling session for anonymous page2012-11-28T09:37:24Z in response to mburatiThanks for the response mburati!
Following this URL resolved my issue