You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-user@portals.apache.org by Duncan Strang <du...@retail-j.com> on 2005/12/01 18:28:02 UTC
Pluto's Service Provider Interface API
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
Re: Pluto 1.1.0-alpha1
Posted by Duong BaTien <du...@gmail.com>.
Thanks David and Zhong. For the benefit of others, followings are
details to make it work.
Edit the following file:
${user.home}/.m2/repository/marmalade/marmalade-taglibs/1.0-alpha-3/marmalade-taglibs-1.0-alpha-3.pom and add <packaging>pom</packaging> then try mvn install again.
BaTien
DBGROUPS
On Mon, 2006-01-30 at 05:07 +0800, Zhong ZHENG wrote:
> Hi,
>
> I got the same error when building pluto. It seems to be an error in
> marmalade-taglibs's pom file. I figured out this issue by doing the
> following:
>
> cd to your maven repo (normally ${user.home}\.m2\repository) and check
> marmalade directory. Edit pom.xml in marmalade-taglibs directory and
> change the package from jar to pom. Then retry mvn install.
>
> Hope that helps.
>
> Regards.
>
> On 1/30/06, David H. DeWolf <dd...@apache.org> wrote:
> There have been reports that the build does not work with the
> most
> recent versions of maven. Try maven 2.0. Sorry, hopefully
> one of us
> will be able to look into this soon!
>
>
> David
>
> Duong BaTien wrote:
> > Greetings and Happy Lunar New Year.
> >
> > I get Pluto 1.1 sources from svn and try to install via mvn
> [$ mvn
> > install] in the directory tags/release-1.1.0-alpha1 and get
> the
> > following error:
> >
> > Project ID: unknown:marmalade-tags-io
> >
> > Reason: Parent: null:marmalade-taglibs:jar:null of project:
> > unknown:marmalade-tags-io has wrong packaging: jar. Must be
> 'pom'.
> >
> >
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException:
> Unable to get
> > dependency information: Unable to read the metadata file for
> artifact
> > 'marmalade:marmalade-tags-io:jar': Parent:
> > null:marmalade-taglibs:jar:null of project:
> unknown:marmalade-tags-io
> > has wrong packaging: jar. Must be 'pom'.
> > marmalade:marmalade-tags-io:jar: 1.0-alpha-3
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> > Path to dependency:
> > 1)
> >
> org.apache.maven.plugins:maven-pluto-plugin:maven-plugin:1.1-SNAPSHOT
> >
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:548)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:472)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> >
> > Does any one have an answer?
> >
> > Thanks
> >
> >
> >
>
>
>
>
> --
> ZHENG Zhong
> - http://heavyz.blogspot.com/
> - http://people.apache.org/~zheng/
Re: Pluto 1.1.0-alpha1
Posted by Zhong ZHENG <he...@gmail.com>.
Hi,
I got the same error when building pluto. It seems to be an error in
marmalade-taglibs's pom file. I figured out this issue by doing the
following:
cd to your maven repo (normally ${user.home}\.m2\repository) and check
marmalade directory. Edit pom.xml in marmalade-taglibs directory and change
the package from jar to pom. Then retry mvn install.
Hope that helps.
Regards.
On 1/30/06, David H. DeWolf <dd...@apache.org> wrote:
>
> There have been reports that the build does not work with the most
> recent versions of maven. Try maven 2.0. Sorry, hopefully one of us
> will be able to look into this soon!
>
>
> David
>
> Duong BaTien wrote:
> > Greetings and Happy Lunar New Year.
> >
> > I get Pluto 1.1 sources from svn and try to install via mvn [$ mvn
> > install] in the directory tags/release-1.1.0-alpha1 and get the
> > following error:
> >
> > Project ID: unknown:marmalade-tags-io
> >
> > Reason: Parent: null:marmalade-taglibs:jar:null of project:
> > unknown:marmalade-tags-io has wrong packaging: jar. Must be 'pom'.
> >
> >
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get
> > dependency information: Unable to read the metadata file for artifact
> > 'marmalade:marmalade-tags-io:jar': Parent:
> > null:marmalade-taglibs:jar:null of project: unknown:marmalade-tags-io
> > has wrong packaging: jar. Must be 'pom'.
> > marmalade:marmalade-tags-io:jar:1.0-alpha-3
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2)
> > Path to dependency:
> > 1)
> > org.apache.maven.plugins:maven-pluto-plugin:maven-plugin:1.1-SNAPSHOT
> >
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:548)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:472)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:451)
> >
> > Does any one have an answer?
> >
> > Thanks
> >
> >
> >
>
>
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/
Re: Pluto 1.1.0-alpha1
Posted by "David H. DeWolf" <dd...@apache.org>.
There have been reports that the build does not work with the most
recent versions of maven. Try maven 2.0. Sorry, hopefully one of us
will be able to look into this soon!
David
Duong BaTien wrote:
> Greetings and Happy Lunar New Year.
>
> I get Pluto 1.1 sources from svn and try to install via mvn [$ mvn
> install] in the directory tags/release-1.1.0-alpha1 and get the
> following error:
>
> Project ID: unknown:marmalade-tags-io
>
> Reason: Parent: null:marmalade-taglibs:jar:null of project:
> unknown:marmalade-tags-io has wrong packaging: jar. Must be 'pom'.
>
>
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get
> dependency information: Unable to read the metadata file for artifact
> 'marmalade:marmalade-tags-io:jar': Parent:
> null:marmalade-taglibs:jar:null of project: unknown:marmalade-tags-io
> has wrong packaging: jar. Must be 'pom'.
> marmalade:marmalade-tags-io:jar:1.0-alpha-3
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> Path to dependency:
> 1)
> org.apache.maven.plugins:maven-pluto-plugin:maven-plugin:1.1-SNAPSHOT
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:548)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
>
> Does any one have an answer?
>
> Thanks
>
>
>
Re: Pluto 1.1.0-alpha1
Posted by Duong BaTien <du...@gmail.com>.
Greetings and Happy Lunar New Year.
I get Pluto 1.1 sources from svn and try to install via mvn [$ mvn
install] in the directory tags/release-1.1.0-alpha1 and get the
following error:
Project ID: unknown:marmalade-tags-io
Reason: Parent: null:marmalade-taglibs:jar:null of project:
unknown:marmalade-tags-io has wrong packaging: jar. Must be 'pom'.
[INFO]
----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get
dependency information: Unable to read the metadata file for artifact
'marmalade:marmalade-tags-io:jar': Parent:
null:marmalade-taglibs:jar:null of project: unknown:marmalade-tags-io
has wrong packaging: jar. Must be 'pom'.
marmalade:marmalade-tags-io:jar:1.0-alpha-3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
Path to dependency:
1)
org.apache.maven.plugins:maven-pluto-plugin:maven-plugin:1.1-SNAPSHOT
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:548)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
Does any one have an answer?
Thanks
Re: Pluto's Service Provider Interface API
Posted by Duncan Strang <du...@retail-j.com>.
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
>
>