[
https://issues.apache.org/struts/browse/WW-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41696
]
Nils-Helge Garli commented on WW-2062:
--------------------------------------
I'm pretty certain this is an uPortal issue. The reason you get different
behaviour with the struts-bridge portlet is that it has expiration cache in
portlet.xml set to -1, whereas the struts2 portlet has expiration cahce set to
0, which means it doesn't cache anything. If you change expiration-cache in
portlet.xml of the struts bridge portlet, you'll experience the same bug. It
also happens with the other JSR168 portlet examples that comes with uPortal.
> Struts2 portlets window states vs uPortal portlal server
> --------------------------------------------------------
>
> Key: WW-2062
> URL: https://issues.apache.org/struts/browse/WW-2062
> Project: Struts 2
> Issue Type: Bug
> Components: Portlet Integration
> Affects Versions: 2.0.6
> Environment: fedora core 5 , java 5, struts 2.0.6, uPortal 2.5.3
> Reporter: tom
> Assignee: Nils-Helge Garli
>
> Struts2 portlets on uPortal does not seem to handle the window states
> properly.
> Other portlet development strategies like struts bridge etc works fine on
> uPortal,
> Already I got a modification in my portlet dispatcher class not to render
> anything when the window state is MINIMIZED, recomended by Nils-Helge
> The behaviour is as follows, when I minmize a portlet, it get mimized, but
> when I try to minimize another portlet that portlet get minimized but the
> earlier portlet get expanded, it does not remain in the previous state, This
> is the major bug
> We have not written any bridges to map between uPortal and S2, we thought we
> dont need any but everything would work.
> Hope this is handled by struts 2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
