> >> > behaviour from server to server.
> > >>
> > >> We have different portlet development
> strategies
> > >> working fine with uPortal, hen
class for each switch
>> between windows states so that in the portet we can do
>> something.
>>
>> Thanks
>>
>>
>>
>>
>>
>>
>>
________________
>> Got a little couch potato?
>> Check out fun summer activi
;
>>
>>
>> ________
>> Got a little couch potato?
>> Check out fun summer activities for kids.
>> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&
I have to correct myself. The dispatcher extends the GenericPortlet
class, but it overrides the render method because of the specialized
mode handling. But the effect is still the same, the window state
logic in doDispatch is not invoked.
Sorry for the confusion.
Nils-H
On 6/26/07, Nils-Helge G
All portlets are responsible for what to render in the different
window states, even when caching is enabled, if the portlet is the
"target" of a user interaction (PLT.18.1 in the spec). But usually
when creating portlets, you extend the GenericPortlet class, which has
built in logic for skipping
> "When a portlet is in MINIMIZED window state, the
> portlet should only render
> minimal output or no output at all."
Ealier we were using struts-bridge for portlet
development, there it was showing no output for the
MINIMIZED window state, also I have seen lot of other
portlet development str
Hi!
To quote the spec:
"When a portlet is in MINIMIZED window state, the portlet should only render
minimal output or no output at all."
As I interpret this, it's the responsibility of the portlet to display the
correct content. So you need to do some checking for the window state and
take acco
Hi,
In Struts2 portlets development, It looks to us that
the minimize does not work as expected, When we presss
the minimize button instead of minimizing it shows the
same content.
to my understanding it should not render anything at
all.
We trying this on uPortal.
Can some one else try these t
8 matches
Mail list logo
