Ah
http://portals.apache.org/pluto/v101/developer/integrate.html
gives me the answers.
Duncan Strang wrote:
Hi (again)
I've been trying to nail down these two interfaces that sit between
the portal and the portlet container.
I think I understand that Pluto's Portlet Container Invoker API is
in fact the PortletContainer interface and the associated
PortletContainerImpl class (and that's it, no other classes are involved)
The Service Provider Interface is a little harder to nail down
I read somewhere that the Service Provider Interface is 'implemented'
by the services that are passed to the portlet container when the
portal first creates it
Looking at the Pluto org.apache.pluto.portalImpl.Servlet class it
appears that a number of services are being created with references to
these services being passed to the container in the
PortletContainerEnvironment Object.
Am I right in assuming that the Pluto Service Provider Interface (the
one that must be implemented by the portal) consists of
org.apache.pluto.services.factory.FactoryManagerService
org.apache.pluto.services.information.InformationProviderService
org.apache.pluto.services.log.LogService
org.apache.pluto.services.property.PropertyManagerService
org.apache.pluto.services.title.DynamicTitleService
If this IS the SPI, why is it that the PropertyManagerService is not
passed to the container from the portal driver ?
Many thanks (again)
Duncan
