Default Portlet State

[Dan Olsen-4]

** High Priority **

I am still not sure how to default all portlets to closed when a user logs in. I have a demo coming up to show the client what I have done so far and we would really like to have the portlets defaulting to closed. Can someone please help me figure this out?
 
I would figured this would be an easy task but I have yet to find any way to make this happen. I really need to get this figured out so any help would be greatly appreciated.

[David Sean Taylor]

On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:

> ** High Priority **
>
> I am still not sure how to default all portlets to closed when a  
> user logs in. I have a demo coming up to show the client what I have  
> done so far and we would really like to have the portlets defaulting  
> to closed. Can someone please help me figure this out?
>
> I would figured this would be an easy task but I have yet to find  
> any way to make this happen. I really need to get this figured out  
> so any help would be greatly appreciated.

Is this for Jetspeed 1.x ?
Not sure what you mean by "closed"



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Andrew Strickland-2]

He means default to minizmized window state.  I've tried to answer this
question twice before...I believe the best possible solution is:

1) add an init parameter to your portlet.xml like "firstView" and set it to
true.  In your portlet class's doRender method check the value of the
initParmater.  If it's true, set window state to minimized and render...if
it's false then do nothing to window state and render.

Andy

On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
wrote:

>
> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>
>  ** High Priority **
> >
> > I am still not sure how to default all portlets to closed when a user
> > logs in. I have a demo coming up to show the client what I have done so far
> > and we would really like to have the portlets defaulting to closed. Can
> > someone please help me figure this out?
> >
> > I would figured this would be an easy task but I have yet to find any
> > way to make this happen. I really need to get this figured out so any help
> > would be greatly appreciated.
> >
>
> Is this for Jetspeed 1.x ?
> Not sure what you mean by "closed"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> For additional commands, e-mail: jetspeed-user-help@...
>
>

[Dan Olsen-4]

But won't this solution render it closed every time it renders? It would make sense if there was a setting for portlets to set the default window state.

>>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
He means default to minizmized window state.  I've tried to answer this
question twice before...I believe the best possible solution is:

1) add an init parameter to your portlet.xml like "firstView" and set it to
true.  In your portlet class's doRender method check the value of the
initParmater.  If it's true, set window state to minimized and render...if
it's false then do nothing to window state and render.

Andy

On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
wrote:

>
> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>
>  ** High Priority **
> >
> > I am still not sure how to default all portlets to closed when a user
> > logs in. I have a demo coming up to show the client what I have done so far
> > and we would really like to have the portlets defaulting to closed. Can
> > someone please help me figure this out?
> >
> > I would figured this would be an easy task but I have yet to find any
> > way to make this happen. I really need to get this figured out so any help
> > would be greatly appreciated.
> >
>
> Is this for Jetspeed 1.x ?
> Not sure what you mean by "closed"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> For additional commands, e-mail: jetspeed-user-help@...
>
>

[Andrew Strickland-2]

If "*firstView*" is true set window state to minimized and then set "*
firstView*" to false, then render...subsequent doViews will check the value
of "*firstView*" (it's now false) and will render with whatever window state
the portal tells it to render with.

On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:

> But won't this solution render it closed every time it renders? It would
> make sense if there was a setting for portlets to set the default window
> state.
>
> >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
> He means default to minizmized window state.  I've tried to answer this
> question twice before...I believe the best possible solution is:
>
> 1) add an init parameter to your portlet.xml like "firstView" and set it
> to
> true.  In your portlet class's doRender method check the value of the
> initParmater.  If it's true, set window state to minimized and render...if
> it's false then do nothing to window state and render.
>
> Andy
>
> On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
> wrote:
>
> >
> > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> >
> >  ** High Priority **
> > >
> > > I am still not sure how to default all portlets to closed when a user
> > > logs in. I have a demo coming up to show the client what I have done
> so far
> > > and we would really like to have the portlets defaulting to closed.
> Can
> > > someone please help me figure this out?
> > >
> > > I would figured this would be an easy task but I have yet to find any
> > > way to make this happen. I really need to get this figured out so any
> help
> > > would be greatly appreciated.
> > >
> >
> > Is this for Jetspeed 1.x ?
> > Not sure what you mean by "closed"
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> > For additional commands, e-mail: jetspeed-user-help@...
> >
> >
>

[Dan Olsen-4]

The problem for me is that I am using Spring to create my portlets. So the class pointed to in my portlet.xml file is org.springframework.web.portlet.DispatcherPortlet.

>>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
If "*firstView*" is true set window state to minimized and then set "*
firstView*" to false, then render...subsequent doViews will check the value
of "*firstView*" (it's now false) and will render with whatever window state
the portal tells it to render with.

On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:

> But won't this solution render it closed every time it renders? It would
> make sense if there was a setting for portlets to set the default window
> state.
>
> >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
> He means default to minizmized window state.  I've tried to answer this
> question twice before...I believe the best possible solution is:
>
> 1) add an init parameter to your portlet.xml like "firstView" and set it
> to
> true.  In your portlet class's doRender method check the value of the
> initParmater.  If it's true, set window state to minimized and render...if
> it's false then do nothing to window state and render.
>
> Andy
>
> On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
> wrote:
>
> >
> > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> >
> >  ** High Priority **
> > >
> > > I am still not sure how to default all portlets to closed when a user
> > > logs in. I have a demo coming up to show the client what I have done
> so far
> > > and we would really like to have the portlets defaulting to closed.
> Can
> > > someone please help me figure this out?
> > >
> > > I would figured this would be an easy task but I have yet to find any
> > > way to make this happen. I really need to get this figured out so any
> help
> > > would be greatly appreciated.
> > >
> >
> > Is this for Jetspeed 1.x ?
> > Not sure what you mean by "closed"
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> > For additional commands, e-mail: jetspeed-user-help@...
> >
> >
>

[Andrew Strickland-2]

So create your own portlet class that extends
org.springframework.web.portlet.DispatcherPortlet.
and override the doView to do the same as the Spring portlet but modify to
add in your handling of the default view state.


On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...> wrote:

> The problem for me is that I am using Spring to create my portlets. So the
> class pointed to in my portlet.xml file is
> org.springframework.web.portlet.DispatcherPortlet.
>
> >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
> If "*firstView*" is true set window state to minimized and then set "*
> firstView*" to false, then render...subsequent doViews will check the
> value
> of "*firstView*" (it's now false) and will render with whatever window
> state
> the portal tells it to render with.
>
> On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:
>
> > But won't this solution render it closed every time it renders? It would
> > make sense if there was a setting for portlets to set the default window
> > state.
> >
> > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
> > He means default to minizmized window state.  I've tried to answer this
> > question twice before...I believe the best possible solution is:
> >
> > 1) add an init parameter to your portlet.xml like "firstView" and set it
> > to
> > true.  In your portlet class's doRender method check the value of the
> > initParmater.  If it's true, set window state to minimized and
> render...if
> > it's false then do nothing to window state and render.
> >
> > Andy
> >
> > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
> david@...>
> > wrote:
> >
> > >
> > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> > >
> > >  ** High Priority **
> > > >
> > > > I am still not sure how to default all portlets to closed when a
> user
> > > > logs in. I have a demo coming up to show the client what I have done
> > so far
> > > > and we would really like to have the portlets defaulting to closed.
> > Can
> > > > someone please help me figure this out?
> > > >
> > > > I would figured this would be an easy task but I have yet to find
> any
> > > > way to make this happen. I really need to get this figured out so
> any
> > help
> > > > would be greatly appreciated.
> > > >
> > >
> > > Is this for Jetspeed 1.x ?
> > > Not sure what you mean by "closed"
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> > > For additional commands, e-mail: jetspeed-user-help@...
> > >
> > >
> >
>

[Dan Olsen-4]

So I have created a class that extends the DispatcherPortlet class. However, for some reason my doView function is not being invoked. I overrode the init function and that is getting invoked. Any idea why my doView function would not be getting invoked?
 
- Dan

>>> "Andrew Strickland" <strickla@...> 4/15/2008 10:11 AM >>>
So create your own portlet class that extends
org.springframework.web.portlet.DispatcherPortlet.
and override the doView to do the same as the Spring portlet but modify to
add in your handling of the default view state.


On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...> wrote:

> The problem for me is that I am using Spring to create my portlets. So the
> class pointed to in my portlet.xml file is
> org.springframework.web.portlet.DispatcherPortlet.
>
> >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
> If "*firstView*" is true set window state to minimized and then set "*
> firstView*" to false, then render...subsequent doViews will check the
> value
> of "*firstView*" (it's now false) and will render with whatever window
> state
> the portal tells it to render with.
>
> On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:
>
> > But won't this solution render it closed every time it renders? It would
> > make sense if there was a setting for portlets to set the default window
> > state.
> >
> > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
> > He means default to minizmized window state.  I've tried to answer this
> > question twice before...I believe the best possible solution is:
> >
> > 1) add an init parameter to your portlet.xml like "firstView" and set it
> > to
> > true.  In your portlet class's doRender method check the value of the
> > initParmater.  If it's true, set window state to minimized and
> render...if
> > it's false then do nothing to window state and render.
> >
> > Andy
> >
> > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
> david@...>
> > wrote:
> >
> > >
> > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> > >
> > >  ** High Priority **
> > > >
> > > > I am still not sure how to default all portlets to closed when a
> user
> > > > logs in. I have a demo coming up to show the client what I have done
> > so far
> > > > and we would really like to have the portlets defaulting to closed.
> > Can
> > > > someone please help me figure this out?
> > > >
> > > > I would figured this would be an easy task but I have yet to find
> any
> > > > way to make this happen. I really need to get this figured out so
> any
> > help
> > > > would be greatly appreciated.
> > > >
> > >
> > > Is this for Jetspeed 1.x ?
> > > Not sure what you mean by "closed"
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> > > For additional commands, e-mail: jetspeed-user-help@...
> > >
> > >
> >
>

[Andrew Strickland-2]

Could be a number of reasons...

Check to make sure you've overridden the method properly including
having the parameters passed in the same order as the
superclass...otherwise you'll just have a very "similar" method.
Swapping the order of the parameters is a common mistake.  If you're
using an IDE that does auto-overide or auto-implementation for you
then I would think this isn't that likely but if you did it by hand
then it could happen.

Make sure you're not calling super.doView(...) at the beginning of
your method.  First you want to do your window state management, and
THEN call super.doView(...) at the end.  If you call it at the
beginning then the super method is almost assuredly returning and
writing to the outputstream before you get the chance to set the
window state.

Make sure your portlet.xml is using your new extended class and not
the Spring portlet class.

Any further guesses would be just that.  If you can provide the code
of your overridden doView it might shed more light.

On Wed, Apr 16, 2008 at 4:35 PM, Dan Olsen <danrolsen@...> wrote:

> So I have created a class that extends the DispatcherPortlet class. However, for some reason my doView function is not being invoked. I overrode the init function and that is getting invoked. Any idea why my doView function would not be getting invoked?
>
>  - Dan
>
>  >>> "Andrew Strickland" <strickla@...> 4/15/2008 10:11 AM >>>
>
>
> So create your own portlet class that extends
>  org.springframework.web.portlet.DispatcherPortlet.
>  and override the doView to do the same as the Spring portlet but modify to
>  add in your handling of the default view state.
>
>
>  On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...> wrote:
>
>  > The problem for me is that I am using Spring to create my portlets. So the
>  > class pointed to in my portlet.xml file is
>  > org.springframework.web.portlet.DispatcherPortlet.
>  >
>  > >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
>  > If "*firstView*" is true set window state to minimized and then set "*
>  > firstView*" to false, then render...subsequent doViews will check the
>  > value
>  > of "*firstView*" (it's now false) and will render with whatever window
>  > state
>  > the portal tells it to render with.
>  >
>  > On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:
>  >
>  > > But won't this solution render it closed every time it renders? It would
>  > > make sense if there was a setting for portlets to set the default window
>  > > state.
>  > >
>  > > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
>  > > He means default to minizmized window state.  I've tried to answer this
>  > > question twice before...I believe the best possible solution is:
>  > >
>  > > 1) add an init parameter to your portlet.xml like "firstView" and set it
>  > > to
>  > > true.  In your portlet class's doRender method check the value of the
>  > > initParmater.  If it's true, set window state to minimized and
>  > render...if
>  > > it's false then do nothing to window state and render.
>  > >
>  > > Andy
>  > >
>  > > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
>  > david@...>
>  > > wrote:
>  > >
>  > > >
>  > > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>  > > >
>  > > >  ** High Priority **
>  > > > >
>  > > > > I am still not sure how to default all portlets to closed when a
>  > user
>  > > > > logs in. I have a demo coming up to show the client what I have done
>  > > so far
>  > > > > and we would really like to have the portlets defaulting to closed.
>  > > Can
>  > > > > someone please help me figure this out?
>  > > > >
>  > > > > I would figured this would be an easy task but I have yet to find
>  > any
>  > > > > way to make this happen. I really need to get this figured out so
>  > any
>  > > help
>  > > > > would be greatly appreciated.
>  > > > >
>  > > >
>  > > > Is this for Jetspeed 1.x ?
>  > > > Not sure what you mean by "closed"
>  > > >
>  > > >
>  > > >
>  > > > ---------------------------------------------------------------------
>  > > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>  > > > For additional commands, e-mail: jetspeed-user-help@...
>  > > >
>  > > >
>  > >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Dan Olsen-4]

Below is the code for my class that is overriding DispatcherPortlet. Any signs of what the problem might be that is causing the doView not to be invoked?
 
/**
 * @author DOLSEN
 *
 */
public class PerformanceManagementPortlet extends DispatcherPortlet {
    String firstView;
 
    @Override
    public void init(PortletConfig config) throws PortletException {
        super.init(config);
        this.firstView = config.getInitParameter("firstView");
    }
 
    @Override
    protected void doView(RenderRequest request, RenderResponse response)
                     throws PortletException, IOException {
        response.setContentType("text/html");
        response.getWriter().write("Start: " + this.firstView);
    }
 
}


>>> "Andrew Strickland" <strickla@...> 4/16/2008 2:43 PM >>>
Could be a number of reasons...

Check to make sure you've overridden the method properly including
having the parameters passed in the same order as the
superclass...otherwise you'll just have a very "similar" method.
Swapping the order of the parameters is a common mistake.  If you're
using an IDE that does auto-overide or auto-implementation for you
then I would think this isn't that likely but if you did it by hand
then it could happen.

Make sure you're not calling super.doView(...) at the beginning of
your method.  First you want to do your window state management, and
THEN call super.doView(...) at the end.  If you call it at the
beginning then the super method is almost assuredly returning and
writing to the outputstream before you get the chance to set the
window state.

Make sure your portlet.xml is using your new extended class and not
the Spring portlet class.

Any further guesses would be just that.  If you can provide the code
of your overridden doView it might shed more light.

On Wed, Apr 16, 2008 at 4:35 PM, Dan Olsen <danrolsen@...> wrote:

> So I have created a class that extends the DispatcherPortlet class. However, for some reason my doView function is not being invoked. I overrode the init function and that is getting invoked. Any idea why my doView function would not be getting invoked?
>
>  - Dan
>
>  >>> "Andrew Strickland" <strickla@...> 4/15/2008 10:11 AM >>>
>
>
> So create your own portlet class that extends
>  org.springframework.web.portlet.DispatcherPortlet.
>  and override the doView to do the same as the Spring portlet but modify to
>  add in your handling of the default view state.
>
>
>  On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...> wrote:
>
>  > The problem for me is that I am using Spring to create my portlets. So the
>  > class pointed to in my portlet.xml file is
>  > org.springframework.web.portlet.DispatcherPortlet.
>  >
>  > >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
>  > If "*firstView*" is true set window state to minimized and then set "*
>  > firstView*" to false, then render...subsequent doViews will check the
>  > value
>  > of "*firstView*" (it's now false) and will render with whatever window
>  > state
>  > the portal tells it to render with.
>  >
>  > On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...> wrote:
>  >
>  > > But won't this solution render it closed every time it renders? It would
>  > > make sense if there was a setting for portlets to set the default window
>  > > state.
>  > >
>  > > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
>  > > He means default to minizmized window state.  I've tried to answer this
>  > > question twice before...I believe the best possible solution is:
>  > >
>  > > 1) add an init parameter to your portlet.xml like "firstView" and set it
>  > > to
>  > > true.  In your portlet class's doRender method check the value of the
>  > > initParmater.  If it's true, set window state to minimized and
>  > render...if
>  > > it's false then do nothing to window state and render.
>  > >
>  > > Andy
>  > >
>  > > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
>  > david@...>
>  > > wrote:
>  > >
>  > > >
>  > > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>  > > >
>  > > >  ** High Priority **
>  > > > >
>  > > > > I am still not sure how to default all portlets to closed when a
>  > user
>  > > > > logs in. I have a demo coming up to show the client what I have done
>  > > so far
>  > > > > and we would really like to have the portlets defaulting to closed.
>  > > Can
>  > > > > someone please help me figure this out?
>  > > > >
>  > > > > I would figured this would be an easy task but I have yet to find
>  > any
>  > > > > way to make this happen. I really need to get this figured out so
>  > any
>  > > help
>  > > > > would be greatly appreciated.
>  > > > >
>  > > >
>  > > > Is this for Jetspeed 1.x ?
>  > > > Not sure what you mean by "closed"
>  > > >
>  > > >
>  > > >
>  > > > ---------------------------------------------------------------------
>  > > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>  > > > For additional commands, e-mail: jetspeed-user-help@...
>  > > >
>  > > >
>  > >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Brad Gardner]

I haven't looked at the spring implementation that you are extending, but
coming from GenericPortlet, it's usually "public void doView" instead of
protected.

On Wed, Apr 16, 2008 at 4:59 PM, Dan Olsen <danrolsen@...> wrote:

> Below is the code for my class that is overriding DispatcherPortlet. Any
> signs of what the problem might be that is causing the doView not to be
> invoked?
>
> /**
>  * @author DOLSEN
>  *
>  */
> public class PerformanceManagementPortlet extends DispatcherPortlet {
>    String firstView;
>
>    @Override
>    public void init(PortletConfig config) throws PortletException {
>        super.init(config);
>        this.firstView = config.getInitParameter("firstView");
>    }
>
>    @Override
>    protected void doView(RenderRequest request, RenderResponse response)
>                     throws PortletException, IOException {
>        response.setContentType("text/html");
>        response.getWriter().write("Start: " + this.firstView);
>    }
>
> }
>
>
> >>> "Andrew Strickland" <strickla@...> 4/16/2008 2:43 PM >>>
> Could be a number of reasons...
>
> Check to make sure you've overridden the method properly including
> having the parameters passed in the same order as the
> superclass...otherwise you'll just have a very "similar" method.
> Swapping the order of the parameters is a common mistake.  If you're
> using an IDE that does auto-overide or auto-implementation for you
> then I would think this isn't that likely but if you did it by hand
> then it could happen.
>
> Make sure you're not calling super.doView(...) at the beginning of
> your method.  First you want to do your window state management, and
> THEN call super.doView(...) at the end.  If you call it at the
> beginning then the super method is almost assuredly returning and
> writing to the outputstream before you get the chance to set the
> window state.
>
> Make sure your portlet.xml is using your new extended class and not
> the Spring portlet class.
>
> Any further guesses would be just that.  If you can provide the code
> of your overridden doView it might shed more light.
>
> On Wed, Apr 16, 2008 at 4:35 PM, Dan Olsen <danrolsen@...> wrote:
> > So I have created a class that extends the DispatcherPortlet class.
> However, for some reason my doView function is not being invoked. I overrode
> the init function and that is getting invoked. Any idea why my doView
> function would not be getting invoked?
> >
> >  - Dan
> >
> >  >>> "Andrew Strickland" <strickla@...> 4/15/2008 10:11 AM >>>
> >
> >
> > So create your own portlet class that extends
> >  org.springframework.web.portlet.DispatcherPortlet.
> >  and override the doView to do the same as the Spring portlet but modify
> to
> >  add in your handling of the default view state.
> >
> >
> >  On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...> wrote:
> >
> >  > The problem for me is that I am using Spring to create my portlets.
> So the
> >  > class pointed to in my portlet.xml file is
> >  > org.springframework.web.portlet.DispatcherPortlet.
> >  >
> >  > >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
> >  > If "*firstView*" is true set window state to minimized and then set
> "*
> >  > firstView*" to false, then render...subsequent doViews will check the
> >  > value
> >  > of "*firstView*" (it's now false) and will render with whatever
> window
> >  > state
> >  > the portal tells it to render with.
> >  >
> >  > On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...>
> wrote:
> >  >
> >  > > But won't this solution render it closed every time it renders? It
> would
> >  > > make sense if there was a setting for portlets to set the default
> window
> >  > > state.
> >  > >
> >  > > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM >>>
> >  > > He means default to minizmized window state.  I've tried to answer
> this
> >  > > question twice before...I believe the best possible solution is:
> >  > >
> >  > > 1) add an init parameter to your portlet.xml like "firstView" and
> set it
> >  > > to
> >  > > true.  In your portlet class's doRender method check the value of
> the
> >  > > initParmater.  If it's true, set window state to minimized and
> >  > render...if
> >  > > it's false then do nothing to window state and render.
> >  > >
> >  > > Andy
> >  > >
> >  > > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
> >  > david@...>
> >  > > wrote:
> >  > >
> >  > > >
> >  > > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> >  > > >
> >  > > >  ** High Priority **
> >  > > > >
> >  > > > > I am still not sure how to default all portlets to closed when
> a
> >  > user
> >  > > > > logs in. I have a demo coming up to show the client what I have
> done
> >  > > so far
> >  > > > > and we would really like to have the portlets defaulting to
> closed.
> >  > > Can
> >  > > > > someone please help me figure this out?
> >  > > > >
> >  > > > > I would figured this would be an easy task but I have yet to
> find
> >  > any
> >  > > > > way to make this happen. I really need to get this figured out
> so
> >  > any
> >  > > help
> >  > > > > would be greatly appreciated.
> >  > > > >
> >  > > >
> >  > > > Is this for Jetspeed 1.x ?
> >  > > > Not sure what you mean by "closed"
> >  > > >
> >  > > >
> >  > > >
> >  > > >
> ---------------------------------------------------------------------
> >  > > > To unsubscribe, e-mail:
> jetspeed-user-unsubscribe@...
> >  > > > For additional commands, e-mail:
> jetspeed-user-help@...
> >  > > >
> >  > > >
> >  > >
> >  >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> For additional commands, e-mail: jetspeed-user-help@...
>
>

--
Brad Gardner

[Brad Gardner]

update:

I was able to go out and check the API, and from what it looks like, the
DispatcherPortlet does (through 2 other classes) inherit its doView from
GenericPortlet, so to override it properly, you should make it public as
opposed to protected.

On Wed, Apr 16, 2008 at 6:11 PM, Brad Gardner <bgardner87@...> wrote:

> I haven't looked at the spring implementation that you are extending, but
> coming from GenericPortlet, it's usually "public void doView" instead of
> protected.
>
>
> On Wed, Apr 16, 2008 at 4:59 PM, Dan Olsen <danrolsen@...> wrote:
>
> > Below is the code for my class that is overriding DispatcherPortlet. Any
> > signs of what the problem might be that is causing the doView not to be
> > invoked?
> >
> > /**
> >  * @author DOLSEN
> >  *
> >  */
> > public class PerformanceManagementPortlet extends DispatcherPortlet {
> >    String firstView;
> >
> >    @Override
> >    public void init(PortletConfig config) throws PortletException {
> >        super.init(config);
> >        this.firstView = config.getInitParameter("firstView");
> >    }
> >
> >    @Override
> >    protected void doView(RenderRequest request, RenderResponse response)
> >                     throws PortletException, IOException {
> >        response.setContentType("text/html");
> >        response.getWriter().write("Start: " + this.firstView);
> >    }
> >
> > }
> >
> >
> > >>> "Andrew Strickland" <strickla@...> 4/16/2008 2:43 PM >>>
> > Could be a number of reasons...
> >
> > Check to make sure you've overridden the method properly including
> > having the parameters passed in the same order as the
> > superclass...otherwise you'll just have a very "similar" method.
> > Swapping the order of the parameters is a common mistake.  If you're
> > using an IDE that does auto-overide or auto-implementation for you
> > then I would think this isn't that likely but if you did it by hand
> > then it could happen.
> >
> > Make sure you're not calling super.doView(...) at the beginning of
> > your method.  First you want to do your window state management, and
> > THEN call super.doView(...) at the end.  If you call it at the
> > beginning then the super method is almost assuredly returning and
> > writing to the outputstream before you get the chance to set the
> > window state.
> >
> > Make sure your portlet.xml is using your new extended class and not
> > the Spring portlet class.
> >
> > Any further guesses would be just that.  If you can provide the code
> > of your overridden doView it might shed more light.
> >
> > On Wed, Apr 16, 2008 at 4:35 PM, Dan Olsen <danrolsen@...> wrote:
> > > So I have created a class that extends the DispatcherPortlet class.
> > However, for some reason my doView function is not being invoked. I overrode
> > the init function and that is getting invoked. Any idea why my doView
> > function would not be getting invoked?
> > >
> > >  - Dan
> > >
> > >  >>> "Andrew Strickland" <strickla@...> 4/15/2008 10:11 AM >>>
> > >
> > >
> > > So create your own portlet class that extends
> > >  org.springframework.web.portlet.DispatcherPortlet.
> > >  and override the doView to do the same as the Spring portlet but
> > modify to
> > >  add in your handling of the default view state.
> > >
> > >
> > >  On Tue, Apr 15, 2008 at 11:59 AM, Dan Olsen <danrolsen@...>
> > wrote:
> > >
> > >  > The problem for me is that I am using Spring to create my portlets.
> > So the
> > >  > class pointed to in my portlet.xml file is
> > >  > org.springframework.web.portlet.DispatcherPortlet.
> > >  >
> > >  > >>> "Andrew Strickland" <strickla@...> 4/15/2008 8:48 AM >>>
> > >  > If "*firstView*" is true set window state to minimized and then set
> > "*
> > >  > firstView*" to false, then render...subsequent doViews will check
> > the
> > >  > value
> > >  > of "*firstView*" (it's now false) and will render with whatever
> > window
> > >  > state
> > >  > the portal tells it to render with.
> > >  >
> > >  > On Tue, Apr 15, 2008 at 10:43 AM, Dan Olsen <danrolsen@...>
> > wrote:
> > >  >
> > >  > > But won't this solution render it closed every time it renders?
> > It would
> > >  > > make sense if there was a setting for portlets to set the default
> > window
> > >  > > state.
> > >  > >
> > >  > > >>> "Andrew Strickland" <strickla@...> 4/14/2008 6:16 PM
> > >>>
> > >  > > He means default to minizmized window state.  I've tried to
> > answer this
> > >  > > question twice before...I believe the best possible solution is:
> > >  > >
> > >  > > 1) add an init parameter to your portlet.xml like "firstView" and
> > set it
> > >  > > to
> > >  > > true.  In your portlet class's doRender method check the value of
> > the
> > >  > > initParmater.  If it's true, set window state to minimized and
> > >  > render...if
> > >  > > it's false then do nothing to window state and render.
> > >  > >
> > >  > > Andy
> > >  > >
> > >  > > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <
> > >  > david@...>
> > >  > > wrote:
> > >  > >
> > >  > > >
> > >  > > > On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
> > >  > > >
> > >  > > >  ** High Priority **
> > >  > > > >
> > >  > > > > I am still not sure how to default all portlets to closed
> > when a
> > >  > user
> > >  > > > > logs in. I have a demo coming up to show the client what I
> > have done
> > >  > > so far
> > >  > > > > and we would really like to have the portlets defaulting to
> > closed.
> > >  > > Can
> > >  > > > > someone please help me figure this out?
> > >  > > > >
> > >  > > > > I would figured this would be an easy task but I have yet to
> > find
> > >  > any
> > >  > > > > way to make this happen. I really need to get this figured
> > out so
> > >  > any
> > >  > > help
> > >  > > > > would be greatly appreciated.
> > >  > > > >
> > >  > > >
> > >  > > > Is this for Jetspeed 1.x ?
> > >  > > > Not sure what you mean by "closed"
> > >  > > >
> > >  > > >
> > >  > > >
> > >  > > >
> > ---------------------------------------------------------------------
> > >  > > > To unsubscribe, e-mail:
> > jetspeed-user-unsubscribe@...
> > >  > > > For additional commands, e-mail:
> > jetspeed-user-help@...
> > >  > > >
> > >  > > >
> > >  > >
> > >  >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> > For additional commands, e-mail: jetspeed-user-help@...
> >
> >
>
>
> --
> Brad Gardner

--
Brad Gardner

[David Sean Taylor]

On Apr 16, 2008, at 3:23 PM, Brad Gardner wrote:

> update:
>
> I was able to go out and check the API, and from what it looks like,  
> the
> DispatcherPortlet does (through 2 other classes) inherit its doView  
> from
> GenericPortlet, so to override it properly, you should make it  
> public as
> opposed to protected.
>

I believe you are supposed to implement the methods below, although it  
was never clear to me why we have to have these "Internal" naming  
conventions

        public ModelAndView handleRenderRequestInternal(RenderRequest  
request, RenderResponse response) throws Exception
        {

     public void handleActionRequestInternal( ActionRequest request,  
ActionResponse response ) throws Exception
     {

see examples here:

http://static.springframework.org/spring/docs/2.5.x/reference/portlet.html

and more info:

http://opensource.atlassian.com/confluence/spring/display/JSR168/Home

There are examples in the j2-admin portlet application source code as  
well as in Bridges source code, see the "springmvc" application there

[johnalewis]

I'm not sure this is a good solution to what Dan is trying to achieve.  
Wouldn't this only present the portlet minimized for the first render
request from the first user after the portal is started?  Not only would
the portlet unminimize itself on the second render request (even if the
user hasn't interacted with the portlet), it would only do that for the
first user since the Portlet is shared by all users.  I am assuming Dan
wants it to be minimized for all users until they interact with the portlet.


Andrew Strickland wrote:

> He means default to minizmized window state.  I've tried to answer this
> question twice before...I believe the best possible solution is:
>
> 1) add an init parameter to your portlet.xml like "firstView" and set it to
> true.  In your portlet class's doRender method check the value of the
> initParmater.  If it's true, set window state to minimized and render...if
> it's false then do nothing to window state and render.
>
> Andy
>
> On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
> wrote:
>
>  
>> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>>
>>  ** High Priority **
>>    
>>> I am still not sure how to default all portlets to closed when a user
>>> logs in. I have a demo coming up to show the client what I have done so far
>>> and we would really like to have the portlets defaulting to closed. Can
>>> someone please help me figure this out?
>>>
>>> I would figured this would be an easy task but I have yet to find any
>>> way to make this happen. I really need to get this figured out so any help
>>> would be greatly appreciated.
>>>
>>>      
>> Is this for Jetspeed 1.x ?
>> Not sure what you mean by "closed"
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>> For additional commands, e-mail: jetspeed-user-help@...
>>
>>
>>    
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Dan Olsen-4]

Another thing I noticed was that the only function I found that could be used to change the window state is in the ActionResponse object which I can only get to when an action occurs. I'm not sure how I would do it when the window originally renders after a user logs in.
 
I am amazed that there is not an easy way to set a default window state in Jetspeed.

>>> John Lewis <jlewis@...> 4/17/2008 11:42 AM >>>
I'm not sure this is a good solution to what Dan is trying to achieve.  
Wouldn't this only present the portlet minimized for the first render
request from the first user after the portal is started?  Not only would
the portlet unminimize itself on the second render request (even if the
user hasn't interacted with the portlet), it would only do that for the
first user since the Portlet is shared by all users.  I am assuming Dan
wants it to be minimized for all users until they interact with the portlet.


Andrew Strickland wrote:

> He means default to minizmized window state.  I've tried to answer this
> question twice before...I believe the best possible solution is:
>
> 1) add an init parameter to your portlet.xml like "firstView" and set it to
> true.  In your portlet class's doRender method check the value of the
> initParmater.  If it's true, set window state to minimized and render...if
> it's false then do nothing to window state and render.
>
> Andy
>
> On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
> wrote:
>
>  
>> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>>
>>  ** High Priority **
>>    
>>> I am still not sure how to default all portlets to closed when a user
>>> logs in. I have a demo coming up to show the client what I have done so far
>>> and we would really like to have the portlets defaulting to closed. Can
>>> someone please help me figure this out?
>>>
>>> I would figured this would be an easy task but I have yet to find any
>>> way to make this happen. I really need to get this figured out so any help
>>> would be greatly appreciated.
>>>
>>>      
>> Is this for Jetspeed 1.x ?
>> Not sure what you mean by "closed"
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>> For additional commands, e-mail: jetspeed-user-help@...
>>
>>
>>    
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Andrew Strickland-2]

It's not just Jetspeed...it's a Portlet 1.0 spec issue.  All portlet
containers (of which Jetspeed, or rather Pluto is one) have this
issue.  And you're right, I forgot again that the ActionResponse is
the only object with the setWindowState method.  I just don't think
this is really possible at this time.  Perhaps Portlet spec 2.0 may
address this...I haven't looked at it.

On Thu, Apr 17, 2008 at 3:40 PM, Dan Olsen <danrolsen@...> wrote:

> Another thing I noticed was that the only function I found that could be used to change the window state is in the ActionResponse object which I can only get to when an action occurs. I'm not sure how I would do it when the window originally renders after a user logs in.
>
>  I am amazed that there is not an easy way to set a default window state in Jetspeed.
>
>  >>> John Lewis <jlewis@...> 4/17/2008 11:42 AM >>>
>
>
> I'm not sure this is a good solution to what Dan is trying to achieve.
>  Wouldn't this only present the portlet minimized for the first render
>  request from the first user after the portal is started?  Not only would
>  the portlet unminimize itself on the second render request (even if the
>  user hasn't interacted with the portlet), it would only do that for the
>  first user since the Portlet is shared by all users.  I am assuming Dan
>  wants it to be minimized for all users until they interact with the portlet.
>
>
>  Andrew Strickland wrote:
>  > He means default to minizmized window state.  I've tried to answer this
>  > question twice before...I believe the best possible solution is:
>  >
>  > 1) add an init parameter to your portlet.xml like "firstView" and set it to
>  > true.  In your portlet class's doRender method check the value of the
>  > initParmater.  If it's true, set window state to minimized and render...if
>  > it's false then do nothing to window state and render.
>  >
>  > Andy
>  >
>  > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
>  > wrote:
>  >
>  >
>  >> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>  >>
>  >>  ** High Priority **
>  >>
>  >>> I am still not sure how to default all portlets to closed when a user
>  >>> logs in. I have a demo coming up to show the client what I have done so far
>  >>> and we would really like to have the portlets defaulting to closed. Can
>  >>> someone please help me figure this out?
>  >>>
>  >>> I would figured this would be an easy task but I have yet to find any
>  >>> way to make this happen. I really need to get this figured out so any help
>  >>> would be greatly appreciated.
>  >>>
>  >>>
>  >> Is this for Jetspeed 1.x ?
>  >> Not sure what you mean by "closed"
>  >>
>  >>
>  >>
>  >> ---------------------------------------------------------------------
>  >> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>  >> For additional commands, e-mail: jetspeed-user-help@...
>  >>
>  >>
>  >>
>  >
>  >
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>  For additional commands, e-mail: jetspeed-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Ate Douma]

Correct, this is a portlet api (1.0) "limitation" and not every easy to overcome without some nasty hacking within the
core of Jetspeed (and Pluto), which of course won't be "portable" at all.

With regards to portlet api 2.0, yes there is potential support for this.
But it concerns using and handling some of the predefined container events (PLT.15.3) which are not required to be
supported. So, it depends on the container if/how these events are fired/delivered.
Rest assured though, Jetspeed definitely *will* support these events once we provide our JSR-286 implementation.

Ate

Andrew Strickland wrote:

> It's not just Jetspeed...it's a Portlet 1.0 spec issue.  All portlet
> containers (of which Jetspeed, or rather Pluto is one) have this
> issue.  And you're right, I forgot again that the ActionResponse is
> the only object with the setWindowState method.  I just don't think
> this is really possible at this time.  Perhaps Portlet spec 2.0 may
> address this...I haven't looked at it.
>
> On Thu, Apr 17, 2008 at 3:40 PM, Dan Olsen <danrolsen@...> wrote:
>> Another thing I noticed was that the only function I found that could be used to change the window state is in the ActionResponse object which I can only get to when an action occurs. I'm not sure how I would do it when the window originally renders after a user logs in.
>>
>>  I am amazed that there is not an easy way to set a default window state in Jetspeed.
>>
>>  >>> John Lewis <jlewis@...> 4/17/2008 11:42 AM >>>
>>
>>
>> I'm not sure this is a good solution to what Dan is trying to achieve.
>>  Wouldn't this only present the portlet minimized for the first render
>>  request from the first user after the portal is started?  Not only would
>>  the portlet unminimize itself on the second render request (even if the
>>  user hasn't interacted with the portlet), it would only do that for the
>>  first user since the Portlet is shared by all users.  I am assuming Dan
>>  wants it to be minimized for all users until they interact with the portlet.
>>
>>
>>  Andrew Strickland wrote:
>>  > He means default to minizmized window state.  I've tried to answer this
>>  > question twice before...I believe the best possible solution is:
>>  >
>>  > 1) add an init parameter to your portlet.xml like "firstView" and set it to
>>  > true.  In your portlet class's doRender method check the value of the
>>  > initParmater.  If it's true, set window state to minimized and render...if
>>  > it's false then do nothing to window state and render.
>>  >
>>  > Andy
>>  >
>>  > On Mon, Apr 14, 2008 at 7:11 PM, David Sean Taylor <david@...>
>>  > wrote:
>>  >
>>  >
>>  >> On Apr 14, 2008, at 2:56 PM, Dan Olsen wrote:
>>  >>
>>  >>  ** High Priority **
>>  >>
>>  >>> I am still not sure how to default all portlets to closed when a user
>>  >>> logs in. I have a demo coming up to show the client what I have done so far
>>  >>> and we would really like to have the portlets defaulting to closed. Can
>>  >>> someone please help me figure this out?
>>  >>>
>>  >>> I would figured this would be an easy task but I have yet to find any
>>  >>> way to make this happen. I really need to get this figured out so any help
>>  >>> would be greatly appreciated.
>>  >>>
>>  >>>
>>  >> Is this for Jetspeed 1.x ?
>>  >> Not sure what you mean by "closed"
>>  >>
>>  >>
>>  >>
>>  >> ---------------------------------------------------------------------
>>  >> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>>  >> For additional commands, e-mail: jetspeed-user-help@...
>>  >>
>>  >>
>>  >>
>>  >
>>  >
>>
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
>>  For additional commands, e-mail: jetspeed-user-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> For additional commands, e-mail: jetspeed-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Jeff P.]

We have a custom built portal built on Jetspeed 2.2. Was there any support added to this version to allow for the setting of the initial window state of a portlet? I checked the spec and the PSML doc and didn't see anything.  We'd like to be able to set the initial window state of one or more portlets on a page to be MINIMIZED.  I know others have asked the question but didn't see any activity on this topic for a while.  Thanks so much.

Ate Douma wrote:

Correct, this is a portlet api (1.0) "limitation" and not every easy to overcome without some nasty hacking within the
core of Jetspeed (and Pluto), which of course won't be "portable" at all.

With regards to portlet api 2.0, yes there is potential support for this.
But it concerns using and handling some of the predefined container events (PLT.15.3) which are not required to be
supported. So, it depends on the container if/how these events are fired/delivered.
Rest assured though, Jetspeed definitely *will* support these events once we provide our JSR-286 implementation.

Ate

[David Sean Taylor-3]

On Nov 4, 2009, at 12:37 PM, Jeff P. wrote:

>
> We have a custom built portal built on Jetspeed 2.2. Was there any  
> support
> added to this version to allow for the setting of the initial window  
> state
> of a portlet? I checked the spec and the PSML doc and didn't see  
> anything.
> We'd like to be able to set the initial window state of one or more  
> portlets
> on a page to be MINIMIZED.  I know others have asked the question  
> but didn't
> see any activity on this topic for a while.  Thanks so much.
>

Not currently. We are discussing adding this feature to the next version

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
For additional commands, e-mail: jetspeed-user-help@...

[Jeff P.]

Thanks. That would be great.

I did find the portlet fragment "state" and tried it with a value of
"hidden".  With Jetspeed 2.2 you only get the portlet action bar but you
can't do anything with it.  This would be exactly what we want if you could
then use the actions to display the portlet.  If it makes sense, I am going
to pursue that path with the possibility of adding the feature to support
additional values along with hidden. If there is an easier approach, let me
know.

Thanks.

On Thu, Nov 19, 2009 at 3:22 PM, David Sean Taylor <d.taylor@...>wrote:

>
> On Nov 4, 2009, at 12:37 PM, Jeff P. wrote:
>
>
>> We have a custom built portal built on Jetspeed 2.2. Was there any support
>> added to this version to allow for the setting of the initial window state
>> of a portlet? I checked the spec and the PSML doc and didn't see anything.
>> We'd like to be able to set the initial window state of one or more
>> portlets
>> on a page to be MINIMIZED.  I know others have asked the question but
>> didn't
>> see any activity on this topic for a while.  Thanks so much.
>>
>>  Not currently. We are discussing adding this feature to the next version
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@...
> For additional commands, e-mail: jetspeed-user-help@...
>
>