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

Invalid Window State and null from portlet to JSP

 
David Yutzy
tumbleweed and gunslinger
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok...

Creating a JSR168 portlet and it works fine in Pluto, but I get the following when I deploy to P7:

ERROR: Content not available. REASONE: Invalid request for a change in window state

Here is what the portlet is supposed to do:

* Display a form
* User clicks find
* Lookup is performed
* Window state in processAction() method of portlet is changed to MAXIMIZED
* I'm guessing this is where the error is occuring

I also think that for the TableContainer, I have some sort of attribute incorrect having to do with one of the *channelsIs* values.

I tried toggling them one way or another without any effect.

I then took out all the window state code from the portlet and now when I submit the form, the lookup succeeds, but the value I set in the processAction into Session isn't found when the portlet is rendered.

Again, this all works perfectly fine in Pluto, so it has to be some sort of Sun Portal specific "something" that I'm missing.

Anyone have any experience in writing JSR 168 portlets for Sun Portal?
 
David Yutzy
tumbleweed and gunslinger
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What I found out was that if you have a portlet that changes window state or needs to pass information from any method (in any scope: Application or Portlet) to a JSP file, state is not persisted in "authlessanonymous" mode, meaning, nobody is logged in.

Once the user logs in, the portlet works as coded.

This is kind of strange since Pluto doesn't ask you to login and the portlet works, so it must maintain session and implement a default login.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic