On Jul 8, 2004, at 7:12 AM, Scott T. Weaver wrote:
I notcied that an evil static factory, JetspeedPortletServices, has crept into PortletApplicationWar. It appears that it is being used to validate that services required by a PortletApp actually exist when creating the app.
I am a heavy -1 on this because:
I found the need for a Service Locator pattern as necessary in order to access it from a portlet, until portlets are ported to components, which is possible, since we currently control construction.
I would like to see this moved into JetpseedPortletFactory and validate services at runtime instead of at deployment. Besides the reasons I have mentioned, this a better approach for the simple reason that if a service is removed AFTER a portlet app is deployed, the portlet app is now in an inconsistent state since the service no longer exists yet your app is still deployed and running.That is a good improvement, I hadn't thought of the removal of a service
Sure, we can go ahead and move it there and get rid of the static factory from the deployment component, No problem at all
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
