getting a portlet to load in maximized state

[advaittrivedi]

Hi All,

I have a portlet which does nothing, but I when I put it on page, I want it in maximized state. For that I have added following in *-object.xml:

<?xml version="1.0" encoding="utf-8"?>


<parent-ref>default.xwiki</parent-ref>
<if-exists>overwrite</if-exists>

<window-name>XWikiWindow</window-name>
<instance-ref>XWikiIFramePortletInstance</instance-ref>
center
100
<supported-window-states>
<window-state>maximized</window-state>
</supported-window-states>




The portlet gets deployed OK on the page when I put war in deploy directory, but it shows in normal mode, also it has minimize and maximize buttons, which should not be there if <supported-window-states> has not included them !

Any ideas?

[den74]

if nothing change on portal 2.4.x (i don't know on 2.6) is not possible to define via configuration file the window's portlet mode.

I had a similar problem and solved defining a new layout having the maximized mode only and setting that layout for the page including my portlet. In that way i can't set normal mode but it wasn't neede to me

[den74]

another way is to force the window state programmaticaly with

setWindowState(WindowState.MAXIMIZED) on ActionResponse

[julien1]

Try using the org.jboss.portal.api.* stuff.

You can have an event listener that listen of PageRenderEvent and change the window state of the portlet to maximized.

There is an example of page render listener that manipulates window states in the core-samples package of the source code.

[den74]

hi julien, i looked for solution you suggested but i find PageRenderEvent just in portal 2.6, so maybe it is valid just from that version on.
Actualli I am using 2.4.0 :( but i will remember when i will upgrade to 2.6, thanks

[advaittrivedi]

den,

your solution: "using setWindowState(WindowState.MAXIMIZED) on ActionResponse" is possible in which life cycle method? If its possible only for processAction than how to trigger it unless user initiates an action?

Thanks & Regards,

[den74]

you are right, i used that way to force the window state during the jsf navigation and not to change the initial state. Sorry for wrong suggestion