Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Unwanted Render Request or caching of display contents

 
Kjeld Sigtermans
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello there,

I have made a JSR 168 portlet that shows some content to its user (View mode). A content manager has access to an extra Configure Mode, in which he or she might add or remove content items. When done, the content manager (also being a user) checks the modification by returning to the View Mode.

The problem is, that the View mode is then still displaying content that was just removed, or it's not showing content that was just added. The technical explanation (I guess) is that the Portal Server simply chooses not to perform an Action Request, but just a Render Request instead because it 'thinks' just showing the View display contents will suffice.

How can I FORCE Portal Server to perform an Action Request (so the Action for the View mode is invoked, which in turn accesses the database to renew the data that is to be displayed)? Or do any other activity to achieve the same result?

I tried setting the <expiration-cache> attribute in portlet.xml to 0 but no effect.

I also tried implementing the IStrutsPrepareRender interface in my Action class and still no cigar (suggestion based on article: http://www-128.ibm.com/developerworks/websphere/library/techarticles/0601_patil/0601_patil.html
section: 'Understanding Struts request processing').

Who can help me with this.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic