You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by tom tom <j_...@yahoo.com> on 2007/06/25 06:55:35 UTC
Minimized Window State NOT working
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 things.
Is there any workaround.
Thanks,
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working
Posted by Nils-Helge Garli <ni...@gmail.com>.
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 Garli <ni...@gmail.com> wrote:
> 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 rendering in the "doDispatch" method when
> the window state is minimized. Quote from the javadoc for
> GenericPortlet:
>
> "If the window state of this portlet is minimized, this method does
> not invoke any of the portlet mode rendering methods."
>
> The Jsr168Dispatcher in Struts 2 does not extend GenericPortlet (it
> just implements the Portlet interface, since the handling of modes is
> a bit different from a "regular" portlet), so this logic is missing.
> This means, that for now, the responsibility of what is rendered in
> the minimized state is up to the developer.
>
> I'll create an improvment request in the JIRA for adding default
> window state handling to the Struts 2 portlet dispatcher.
>
> For now, a workaround would be to subclass the Jsr168Dispatcher (or
> modify it directly) and in the render method, do something like
>
> if(!request.getWindowState().equals(WindowState.MINIMIZED)) {
> super.render(request, response);
> }
>
> Nils-H
>
> On 6/26/07, tom tom <j_...@yahoo.com> wrote:
> >
> > > "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 strategies where it shows nothing
> > for the minimized window state.
> >
> > > 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 according action in your portlet.
> >
> > I DONT THINK this is possible, The reason is as
> > follows.
> >
> > In S2 when I submit a form (not a HREF) it goes to an
> > action and there after forward to a JSP, Now being in
> > the same page if I switch between modes, it does not
> > go the action class but shows the content probably
> > from cache or already rendered content, Due to this
> > reason how can I check for the Window State in the
> > corresponding action class.
> >
> >
> >
> >
> >
> > >
> > > However, there wasn't much information about the
> > > minimized window state in
> > > the spec. I couldn't find any description of the
> > > contract between the portal
> > > server's "window buttons" and the window states, so
> > > there might be different
> > > behaviour from server to server.
> >
> > We have different portlet development strategies
> > working fine with uPortal, hence this is nothing to do
> > with the uPortal or any other portal container.
> >
> >
> >
> > Please let me know if any way around for this.
> > This should be a common problem to anyone, Can we
> > enforce it to hit the action 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 activities for kids.
> > http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working-NOT SOLVED
Posted by tom tom <j_...@yahoo.com>.
I doubt, the reason is, before struts 2, we developed
all portlets using struts-bridge, there the
functionality works fine same container, Due to this
reason I dont think this is a portal container bug.
It looks to me for some reason for previously
minimized portlets in render method it gives as
'normal' for the window state.
It gives minimized only for the recently minimized
portlet.
Let me know how to proceed on this.
--- Nils-Helge Garli <ni...@gmail.com> wrote:
> Hi!
>
> I just tried, and the proposed solution works nicely
> in pluto, even
> when a user minimizes another portlet. So it might
> be a container bug.
> Try your portlets in a different container and see
> if the problem
> persists, or attach a debugger and try to figure out
> what information
> is set on the request when the "render" method is
> invoked.
>
> Nils-H
>
> On 7/9/07, Tracy12 <j_...@yahoo.com> wrote:
> >
> > Yes it appeared everything is fine as per the
> following solution, but that is
> > not the case.
> >
> > What happens is, This will work only for the
> portlet where user just
> > minimized. If user tries to minimize another
> portlet the previous one get
> > Expanded, It looks to me server is not detected
> the portlet has allready
> > been minized. For correct functionaliy the server
> should be remembering this
> > information.
> >
> > Is this a bug some where?
> >
> > Let me know how to proceed on this.
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> > Nils-Helge Garli wrote:
> > >
> > > 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 rendering in the
> "doDispatch" method when
> > > the window state is minimized. Quote from the
> javadoc for
> > > GenericPortlet:
> > >
> > > "If the window state of this portlet is
> minimized, this method does
> > > not invoke any of the portlet mode rendering
> methods."
> > >
> > > The Jsr168Dispatcher in Struts 2 does not extend
> GenericPortlet (it
> > > just implements the Portlet interface, since the
> handling of modes is
> > > a bit different from a "regular" portlet), so
> this logic is missing.
> > > This means, that for now, the responsibility of
> what is rendered in
> > > the minimized state is up to the developer.
> > >
> > > I'll create an improvment request in the JIRA
> for adding default
> > > window state handling to the Struts 2 portlet
> dispatcher.
> > >
> > > For now, a workaround would be to subclass the
> Jsr168Dispatcher (or
> > > modify it directly) and in the render method, do
> something like
> > >
> > >
>
if(!request.getWindowState().equals(WindowState.MINIMIZED))
> {
> > > super.render(request, response);
> > > }
> > >
> > > Nils-H
> > >
> > > On 6/26/07, tom tom <j_...@yahoo.com> wrote:
> > >>
> > >> > "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 strategies where it shows
> nothing
> > >> for the minimized window state.
> > >>
> > >> > 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 according action in your portlet.
> > >>
> > >> I DONT THINK this is possible, The reason is as
> > >> follows.
> > >>
> > >> In S2 when I submit a form (not a HREF) it goes
> to an
> > >> action and there after forward to a JSP, Now
> being in
> > >> the same page if I switch between modes, it
> does not
> > >> go the action class but shows the content
> probably
> > >> from cache or already rendered content, Due to
> this
> > >> reason how can I check for the Window State in
> the
> > >> corresponding action class.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> >
> > >> > However, there wasn't much information about
> the
> > >> > minimized window state in
> > >> > the spec. I couldn't find any description of
> the
> > >> > contract between the portal
> > >> > server's "window buttons" and the window
> states, so
> > >> > there might be different
> > >> > behaviour from server to server.
> > >>
> > >> We have different portlet development
> strategies
> > >> working fine with uPortal, hence this is
> nothing to do
> > >> with the uPortal or any other portal container.
> > >>
> > >>
> > >>
> > >> Please let me know if any way around for this.
> > >> This should be a common problem to anyone, Can
> we
> > >> enforce it to hit the action 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 activities for kids.
> > >>
>
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
> > >>
> > >>
>
---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> user-unsubscribe@struts.apache.org
> > >> For additional commands, e-mail:
> user-help@struts.apache.org
> > >>
> > >>
> > >
> > >
>
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> user-unsubscribe@struts.apache.org
> > > For additional commands, e-mail:
> user-help@struts.apache.org
> > >
> > >
> > >
> >
> > --
> > View this message in context:
>
http://www.nabble.com/Minimized-Window-State-NOT-working-tf3974216.html#a11496664
>
=== message truncated ===
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working-NOT SOLVED
Posted by Nils-Helge Garli <ni...@gmail.com>.
Hi!
I just tried, and the proposed solution works nicely in pluto, even
when a user minimizes another portlet. So it might be a container bug.
Try your portlets in a different container and see if the problem
persists, or attach a debugger and try to figure out what information
is set on the request when the "render" method is invoked.
Nils-H
On 7/9/07, Tracy12 <j_...@yahoo.com> wrote:
>
> Yes it appeared everything is fine as per the following solution, but that is
> not the case.
>
> What happens is, This will work only for the portlet where user just
> minimized. If user tries to minimize another portlet the previous one get
> Expanded, It looks to me server is not detected the portlet has allready
> been minized. For correct functionaliy the server should be remembering this
> information.
>
> Is this a bug some where?
>
> Let me know how to proceed on this.
>
> Thanks
>
>
>
>
>
>
> Nils-Helge Garli wrote:
> >
> > 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 rendering in the "doDispatch" method when
> > the window state is minimized. Quote from the javadoc for
> > GenericPortlet:
> >
> > "If the window state of this portlet is minimized, this method does
> > not invoke any of the portlet mode rendering methods."
> >
> > The Jsr168Dispatcher in Struts 2 does not extend GenericPortlet (it
> > just implements the Portlet interface, since the handling of modes is
> > a bit different from a "regular" portlet), so this logic is missing.
> > This means, that for now, the responsibility of what is rendered in
> > the minimized state is up to the developer.
> >
> > I'll create an improvment request in the JIRA for adding default
> > window state handling to the Struts 2 portlet dispatcher.
> >
> > For now, a workaround would be to subclass the Jsr168Dispatcher (or
> > modify it directly) and in the render method, do something like
> >
> > if(!request.getWindowState().equals(WindowState.MINIMIZED)) {
> > super.render(request, response);
> > }
> >
> > Nils-H
> >
> > On 6/26/07, tom tom <j_...@yahoo.com> wrote:
> >>
> >> > "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 strategies where it shows nothing
> >> for the minimized window state.
> >>
> >> > 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 according action in your portlet.
> >>
> >> I DONT THINK this is possible, The reason is as
> >> follows.
> >>
> >> In S2 when I submit a form (not a HREF) it goes to an
> >> action and there after forward to a JSP, Now being in
> >> the same page if I switch between modes, it does not
> >> go the action class but shows the content probably
> >> from cache or already rendered content, Due to this
> >> reason how can I check for the Window State in the
> >> corresponding action class.
> >>
> >>
> >>
> >>
> >>
> >> >
> >> > However, there wasn't much information about the
> >> > minimized window state in
> >> > the spec. I couldn't find any description of the
> >> > contract between the portal
> >> > server's "window buttons" and the window states, so
> >> > there might be different
> >> > behaviour from server to server.
> >>
> >> We have different portlet development strategies
> >> working fine with uPortal, hence this is nothing to do
> >> with the uPortal or any other portal container.
> >>
> >>
> >>
> >> Please let me know if any way around for this.
> >> This should be a common problem to anyone, Can we
> >> enforce it to hit the action 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 activities for kids.
> >> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: user-help@struts.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Minimized-Window-State-NOT-working-tf3974216.html#a11496664
> Sent from the Struts - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working-NOT SOLVED
Posted by Tracy12 <j_...@yahoo.com>.
Yes it appeared everything is fine as per the following solution, but that is
not the case.
What happens is, This will work only for the portlet where user just
minimized. If user tries to minimize another portlet the previous one get
Expanded, It looks to me server is not detected the portlet has allready
been minized. For correct functionaliy the server should be remembering this
information.
Is this a bug some where?
Let me know how to proceed on this.
Thanks
Nils-Helge Garli wrote:
>
> 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 rendering in the "doDispatch" method when
> the window state is minimized. Quote from the javadoc for
> GenericPortlet:
>
> "If the window state of this portlet is minimized, this method does
> not invoke any of the portlet mode rendering methods."
>
> The Jsr168Dispatcher in Struts 2 does not extend GenericPortlet (it
> just implements the Portlet interface, since the handling of modes is
> a bit different from a "regular" portlet), so this logic is missing.
> This means, that for now, the responsibility of what is rendered in
> the minimized state is up to the developer.
>
> I'll create an improvment request in the JIRA for adding default
> window state handling to the Struts 2 portlet dispatcher.
>
> For now, a workaround would be to subclass the Jsr168Dispatcher (or
> modify it directly) and in the render method, do something like
>
> if(!request.getWindowState().equals(WindowState.MINIMIZED)) {
> super.render(request, response);
> }
>
> Nils-H
>
> On 6/26/07, tom tom <j_...@yahoo.com> wrote:
>>
>> > "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 strategies where it shows nothing
>> for the minimized window state.
>>
>> > 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 according action in your portlet.
>>
>> I DONT THINK this is possible, The reason is as
>> follows.
>>
>> In S2 when I submit a form (not a HREF) it goes to an
>> action and there after forward to a JSP, Now being in
>> the same page if I switch between modes, it does not
>> go the action class but shows the content probably
>> from cache or already rendered content, Due to this
>> reason how can I check for the Window State in the
>> corresponding action class.
>>
>>
>>
>>
>>
>> >
>> > However, there wasn't much information about the
>> > minimized window state in
>> > the spec. I couldn't find any description of the
>> > contract between the portal
>> > server's "window buttons" and the window states, so
>> > there might be different
>> > behaviour from server to server.
>>
>> We have different portlet development strategies
>> working fine with uPortal, hence this is nothing to do
>> with the uPortal or any other portal container.
>>
>>
>>
>> Please let me know if any way around for this.
>> This should be a common problem to anyone, Can we
>> enforce it to hit the action 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 activities for kids.
>> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Minimized-Window-State-NOT-working-tf3974216.html#a11496664
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working
Posted by Nils-Helge Garli <ni...@gmail.com>.
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 rendering in the "doDispatch" method when
the window state is minimized. Quote from the javadoc for
GenericPortlet:
"If the window state of this portlet is minimized, this method does
not invoke any of the portlet mode rendering methods."
The Jsr168Dispatcher in Struts 2 does not extend GenericPortlet (it
just implements the Portlet interface, since the handling of modes is
a bit different from a "regular" portlet), so this logic is missing.
This means, that for now, the responsibility of what is rendered in
the minimized state is up to the developer.
I'll create an improvment request in the JIRA for adding default
window state handling to the Struts 2 portlet dispatcher.
For now, a workaround would be to subclass the Jsr168Dispatcher (or
modify it directly) and in the render method, do something like
if(!request.getWindowState().equals(WindowState.MINIMIZED)) {
super.render(request, response);
}
Nils-H
On 6/26/07, tom tom <j_...@yahoo.com> wrote:
>
> > "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 strategies where it shows nothing
> for the minimized window state.
>
> > 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 according action in your portlet.
>
> I DONT THINK this is possible, The reason is as
> follows.
>
> In S2 when I submit a form (not a HREF) it goes to an
> action and there after forward to a JSP, Now being in
> the same page if I switch between modes, it does not
> go the action class but shows the content probably
> from cache or already rendered content, Due to this
> reason how can I check for the Window State in the
> corresponding action class.
>
>
>
>
>
> >
> > However, there wasn't much information about the
> > minimized window state in
> > the spec. I couldn't find any description of the
> > contract between the portal
> > server's "window buttons" and the window states, so
> > there might be different
> > behaviour from server to server.
>
> We have different portlet development strategies
> working fine with uPortal, hence this is nothing to do
> with the uPortal or any other portal container.
>
>
>
> Please let me know if any way around for this.
> This should be a common problem to anyone, Can we
> enforce it to hit the action 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 activities for kids.
> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working
Posted by tom tom <j_...@yahoo.com>.
> "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 strategies where it shows nothing
for the minimized window state.
> 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 according action in your portlet.
I DONT THINK this is possible, The reason is as
follows.
In S2 when I submit a form (not a HREF) it goes to an
action and there after forward to a JSP, Now being in
the same page if I switch between modes, it does not
go the action class but shows the content probably
from cache or already rendered content, Due to this
reason how can I check for the Window State in the
corresponding action class.
>
> However, there wasn't much information about the
> minimized window state in
> the spec. I couldn't find any description of the
> contract between the portal
> server's "window buttons" and the window states, so
> there might be different
> behaviour from server to server.
We have different portlet development strategies
working fine with uPortal, hence this is nothing to do
with the uPortal or any other portal container.
Please let me know if any way around for this.
This should be a common problem to anyone, Can we
enforce it to hit the action 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 activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Minimized Window State NOT working
Posted by Nils-Helge Garli <ni...@gmail.com>.
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 according action in your portlet.
However, there wasn't much information about the minimized window state in
the spec. I couldn't find any description of the contract between the portal
server's "window buttons" and the window states, so there might be different
behaviour from server to server. Have you tried deploying to a different
container, for instance pluto?
Nils-H
On 6/25/07, tom tom <j_...@yahoo.com> wrote:
>
> 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 things.
>
> Is there any workaround.
>
> Thanks,
>
>
>
>
> ____________________________________________________________________________________
> 8:00? 8:25? 8:40? Find a flick in no time
> with the Yahoo! Search movie showtime shortcut.
> http://tools.search.yahoo.com/shortcuts/#news
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>