You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Peter Meier <pe...@tec.govt.nz> on 2005/01/31 22:40:07 UTC
J2: Portlet Life Cycle
Apparently portlets are not instantiated before the portlet container
determines the portlet is needed to service a request, e.g. a render
request. Is there a way to configure the portlet container to load and
instantiate the portlet when it (the portlet container) starts the
portlet application? I assume that the portlet application is loaded
when the portal server builds up information about a portal page and
about the portlets its fragments pointing to, including PortletWindow,
PortletDefinition. But apparently PortletDefinition is not completed
before the portlet is actually instantiated, i.e. the portlet class
loader is then set.
Regards,
Peter
Architect,
TEC
Wellington, New Zealand
email: peter.meier@tec.govt.nz
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2: Portlet Life Cycle
Posted by Peter Meier <pe...@tec.govt.nz>.
You have definitively my vote.
Peter.
David Sean Taylor wrote:
> Peter Meier wrote:
>
>> Apparently portlets are not instantiated before the portlet container
>> determines the portlet is needed to service a request, e.g. a render
>> request. Is there a way to configure the portlet container to load
>> and instantiate the portlet when it (the portlet container) starts
>> the portlet application? I assume that the portlet application is
>> loaded when the portal server builds up information about a portal
>> page and about the portlets its fragments pointing to, including
>> PortletWindow, PortletDefinition. But apparently PortletDefinition is
>> not completed before the portlet is actually instantiated, i.e. the
>> portlet class loader is then set.
>
>
> Yes, thats correct.
> How does everyone feel about a init-on-startup flag in the
> jetspeed-portlet.xml?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: latest FileSystemPAM mods
Posted by "Scott T. Weaver" <sc...@binary-designs.net>.
That was if somehow a portlet app was being deployed and the app already
existed, i.e. deploy somehow fired in favor of redeploy. I think it was
there to support a very slim chance of this happening. I don't think you
need to worry about porting it.
Randy Watler wrote:
> Scott,
>
> I am confused by this change to FileSystemPAM:
>
> @@ -387,6 +387,12 @@
> // save it to the registry
> log.info("Saving the portlet.xml in the registry...");
> + if(registry.namedPortletApplicationExists(app.getName()))
> + {
> + log.warn("Deployment has found an app with the application name,
> "+app.getName()+
> + ". The existing app will be removed in favor of this one.");
> + undeploy(paWar);
> + }
> registry.registerPortletApplication(app);
> log.info("Committing registry changes...");
>
>
> I would like this logic to somehow be moved to the
> DeployPortletAppEventListener instead of bailing out in the middle of
> a registration process here by undeploying. Under what conditions were
> you trying to undeploy here? I do not understand how this could even
> happen unless there were some kind of race condition involved... what
> am I missing?
>
> I was not able to port this change forward into my version of
> FileSystemPAM. We need to resolve this issue if we need to preserve
> this functionality.
>
> Randy
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>
--
"Great minds discuss ideas. Average minds discuss events. Small minds discuss people." - Admiral Hyman Rickover
*******************************************
* Scott T. Weaver *
* <we...@apache.org> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEdit, Website Content Management *
* <http://www.openedit.org> *
*******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
latest FileSystemPAM mods
Posted by Randy Watler <wa...@wispertel.net>.
Scott,
I am confused by this change to FileSystemPAM:
@@ -387,6 +387,12 @@
// save it to the registry
log.info("Saving the portlet.xml in the registry...");
+ if(registry.namedPortletApplicationExists(app.getName()))
+ {
+ log.warn("Deployment has found an app with the application name, "+app.getName()+
+ ". The existing app will be removed in favor of this one.");
+ undeploy(paWar);
+ }
registry.registerPortletApplication(app);
log.info("Committing registry changes...");
I would like this logic to somehow be moved to the
DeployPortletAppEventListener instead of bailing out in the middle of a
registration process here by undeploying. Under what conditions were you
trying to undeploy here? I do not understand how this could even happen
unless there were some kind of race condition involved... what am I missing?
I was not able to port this change forward into my version of
FileSystemPAM. We need to resolve this issue if we need to preserve this
functionality.
Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2: Portlet Life Cycle
Posted by Ate Douma <at...@douma.nu>.
+1
David Sean Taylor wrote:
> Peter Meier wrote:
>
>> Apparently portlets are not instantiated before the portlet container
>> determines the portlet is needed to service a request, e.g. a render
>> request. Is there a way to configure the portlet container to load and
>> instantiate the portlet when it (the portlet container) starts the
>> portlet application? I assume that the portlet application is loaded
>> when the portal server builds up information about a portal page and
>> about the portlets its fragments pointing to, including PortletWindow,
>> PortletDefinition. But apparently PortletDefinition is not completed
>> before the portlet is actually instantiated, i.e. the portlet class
>> loader is then set.
>
>
> Yes, thats correct.
> How does everyone feel about a init-on-startup flag in the
> jetspeed-portlet.xml?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2: Portlet Life Cycle
Posted by Roger Ruttimann <ro...@apache.org>.
+1
David Sean Taylor wrote:
> Peter Meier wrote:
>
>> Apparently portlets are not instantiated before the portlet container
>> determines the portlet is needed to service a request, e.g. a render
>> request. Is there a way to configure the portlet container to load
>> and instantiate the portlet when it (the portlet container) starts
>> the portlet application? I assume that the portlet application is
>> loaded when the portal server builds up information about a portal
>> page and about the portlets its fragments pointing to, including
>> PortletWindow, PortletDefinition. But apparently PortletDefinition is
>> not completed before the portlet is actually instantiated, i.e. the
>> portlet class loader is then set.
>
>
> Yes, thats correct.
> How does everyone feel about a init-on-startup flag in the
> jetspeed-portlet.xml?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2: Portlet Life Cycle
Posted by David Sean Taylor <da...@bluesunrise.com>.
Peter Meier wrote:
> Apparently portlets are not instantiated before the portlet container
> determines the portlet is needed to service a request, e.g. a render
> request. Is there a way to configure the portlet container to load and
> instantiate the portlet when it (the portlet container) starts the
> portlet application? I assume that the portlet application is loaded
> when the portal server builds up information about a portal page and
> about the portlets its fragments pointing to, including PortletWindow,
> PortletDefinition. But apparently PortletDefinition is not completed
> before the portlet is actually instantiated, i.e. the portlet class
> loader is then set.
Yes, thats correct.
How does everyone feel about a init-on-startup flag in the
jetspeed-portlet.xml?
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org