Using the Management Portlet, I created a new portal and added a few portlet instances, including the UserPortletWindow, to the default page. When I display the default page on my new portal, I get the following exception:
2006-08-10 13:19:28,578 ERROR [STDERR] javax.portlet.WindowStateException: Not supported
2006-08-10 13:19:28,578 ERROR [STDERR] at org.jboss.portal.portlet.impl.jsr168.PortletURLImpl.setWindowState(PortletURLImpl.java:68)
2006-08-10 13:19:28,578 ERROR [STDERR] at org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag.setWindowState(GenerateURLTag.java:242)
2006-08-10 13:19:28,578 ERROR [STDERR] at org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag.doEndTag(GenerateURLTag.java:315)
2006-08-10 13:19:28,578 ERROR [STDERR] at org.apache.jsp.WEB_002dINF.jsp.user.menu_jsp._jspx_meth_portlet_renderURL_0(menu_jsp.java:185)
2006-08-10 13:19:28,578 ERROR [STDERR] at org.apache.jsp.WEB_002dINF.jsp.user.menu_jsp._jspService(menu_jsp.java:80)
2006-08-10 13:19:28,578 ERROR [STDERR] at org.jboss.portal.core.servlet.jsp.PortalJsp.service(PortalJsp.java:153)
Looking into the JSP, the error is coming from this line:
<a id="editprofile" href="<portlet:renderURL windowState="maximized"><portlet:param name="op" value="showProfile"/></portlet:renderURL>">
Now, why would "maximized" be an invalid Window state? (By the way, the above errors occur when I am logged in to the portal. If I am not logged in, I get a similar error, but from login.jsp, once again on the portlet:renderURL tag.)
Further research leads me to believe that there are no valid states on any of the portlet instances in the new portal. I say this because the portlet that did work do not have the maximize, minimize, edit or help buttons in the title bar. Is this s bug in 2.4.0.CR3, or is there something I missed in setting up the new portal?
JBoss AS 4.0.4.GA, JBoss Portal 2.4.0.CR3
