On Nov 22, 2009, at 12:43 AM, Ron McNulty wrote:
Hi Mansour
A bit of experimentation and a careful read of JSR 168 and JSR 286
lead me to believe that this is not a standard thing to do.
- NORMAL, MAXIMIZED and MINIMIZED are <window-state> values, not
<portlet-mode> values.
- JSR 168 is a bit ambiguous about window states, but JSR 286 states
that all portlets must support NORMAL, MAXIMIZED and MINIMIZED at a
minimum, so they need not be defined. It seems to make no provision
for turning off support for any of these window states.
So for now I am back to the custom decorator...
I find the whole action processing in Jetspeed annoying. I have
created an issue to re-implement actions in a less complicated, more
easily configurable manner (JS2-1059). The most obvious approach I
took was to comment out the maximize window in jetspeed.properties:
# supported.windowstate = maximized
However doing so has absolutely no effect.
Recommend writing your own custom decorator factory and set it in your
portlet decorator:
actions
.factory=org.apache.jetspeed.decoration.ClearDecoratorActionsFactory
Currently, the factory class is the best place to implement custom
action filtering and behavior
If you working off the trunk, there are a few new features in progress:
# option.actions valid values are: show | hide | dropdown | hover
(default=show)
option.actions=hide
# option.title valid values are: show | hide (default=show)
option.title=show
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
