Hi Glarenzie I would be very interested in seeing your solution as I am trying to achieve the same thing.
I am a JBoss portal newbie so I did not want to create my own layout on my first attempt. Instead I modified the generic layout in portal-core.war/WEB-INF/portal-layouts.xml to include a uri state mapping to my custom layout jsp print.jsp. | <layout> | <name>generic</name> | <uri>/layouts/generic/index.jsp</uri> | <uri state="maximized">/layouts/generic/maximized.jsp</uri> | <uri state="print">/layouts/generic/print.jsp</uri> | <regions> | <region name="left"/> | <region name="center"/> | </regions> | </layout> | I then also modified portal-core.war/WEB-INF/portlet.xml to include a custom window state called print as follows: | <custom-window-state> | <description>print view</description> | <window-state>print</window-state> | </custom-window-state> | In my own portlet, when I switch the window state to print (via processAction) the layout is not mapped to print.jsp but to index.jsp. I'm clearly missing a step. My new window state is being registered as when I obtain the PortalContext from the ActionRequest and then iterate over the supported window states, my custom state is included. I can't seem to map the layout to print.jsp however. Help would be appreciated! Regards Allan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069531#4069531 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069531 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
