You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Ethan Adams <et...@gmail.com> on 2007/02/08 17:36:44 UTC
GenericPortlet init() behavior
I have noticed that the init() method in GenericPortlet doesn't get called
until after the portlet is actually accessed through the Portal. Anyway to
make that get called upon porlet "initialization?"
BTW...This is in Jetspeed-2.0. Not sure if it happens in 2.1
Re: GenericPortlet init() behavior
Posted by Aaron Evans <aa...@gmail.com>.
I just use the servlet context listener in my portlet app to
initialize any application resources...
On 2/8/07, Ethan Adams <et...@gmail.com> wrote:
> I can accomplish what I need through a Servlet in the PortletApplication.
> So, it really isn't necessary.
>
>
> On 2/8/07, David Sean Taylor <da...@bluesunrise.com> wrote:
> >
> >
> > On Feb 8, 2007, at 8:36 AM, Ethan Adams wrote:
> >
> > > I have noticed that the init() method in GenericPortlet doesn't get
> > > called
> > > until after the portlet is actually accessed through the Portal.
> > > Anyway to
> > > make that get called upon porlet "initialization?"
> > >
> > > BTW...This is in Jetspeed-2.0. Not sure if it happens in 2.1
> >
> > At portal initialization phase, we would have to go thru all the
> > registered portlets and initialize them
> > Seems like this could be an optional deployment descriptor, or a
> > portal-wide configuration option
> > I don't think Im going to have time to implement that before the release
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: GenericPortlet init() behavior
Posted by Ethan Adams <et...@gmail.com>.
I can accomplish what I need through a Servlet in the PortletApplication.
So, it really isn't necessary.
On 2/8/07, David Sean Taylor <da...@bluesunrise.com> wrote:
>
>
> On Feb 8, 2007, at 8:36 AM, Ethan Adams wrote:
>
> > I have noticed that the init() method in GenericPortlet doesn't get
> > called
> > until after the portlet is actually accessed through the Portal.
> > Anyway to
> > make that get called upon porlet "initialization?"
> >
> > BTW...This is in Jetspeed-2.0. Not sure if it happens in 2.1
>
> At portal initialization phase, we would have to go thru all the
> registered portlets and initialize them
> Seems like this could be an optional deployment descriptor, or a
> portal-wide configuration option
> I don't think Im going to have time to implement that before the release
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: GenericPortlet init() behavior
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Feb 8, 2007, at 8:36 AM, Ethan Adams wrote:
> I have noticed that the init() method in GenericPortlet doesn't get
> called
> until after the portlet is actually accessed through the Portal.
> Anyway to
> make that get called upon porlet "initialization?"
>
> BTW...This is in Jetspeed-2.0. Not sure if it happens in 2.1
At portal initialization phase, we would have to go thru all the
registered portlets and initialize them
Seems like this could be an optional deployment descriptor, or a
portal-wide configuration option
I don't think Im going to have time to implement that before the release
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org