You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-user@portals.apache.org by Kevin Irmscher <ke...@gmail.com> on 2007/02/01 10:32:09 UTC
Re: Proxy Portlet
On 1/31/07, Diego Louzán <dl...@apache.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kevin Irmscher escribió:
> > Hi!
> >
> > Is the Consumer Proxy Portlet coming with WSRP4J JSR 168 compliant or
> > is it customized for the Pluto portal. I tried to deploy it to the
> > Liferay portal and to the Exo portlet container but neither of them
> > did work. Do you plan to make the Proxy Portlet work with other
> > containers or do you focus on Pluto?
> >
> > Regards,
> > Kevin
>
> The ProxyPortlet is JSR-168 compliant, in fact we have just made it
> independent from Pluto. If you include the exception you are getting
> maybe we can help you. As long as you don't use the Producer Templates,
> which are portal-dependent, you should be able to deploy the portlet on
> any portal.
>
> Regards.
> Diego.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFwOBGgyzZYflJelERAjWUAJ9jSkjigRz2m6JOqr/9X9O+ir14dgCgka6D
> tAvI3oUG6YPPBBBiGYlPKy8=
> =pJAR
> -----END PGP SIGNATURE-----
>
I tried to deploy wsrp4j-proxyportlet.war to Liferay 4.2.1 portal and
get the following exception:
09:10:58,507 INFO [AutoDeployPortletListener:88] Portlets for
\home\liferay\deploy\wsrp4j-proxyportlet.war copied successfully
09:11:01,813 INFO [HotDeployPortletListener:129] Registering portlets for wsrp4
j-proxyportlet
09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name ProducerC
onfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not have a mat
ching entry in liferay-portlet.xml
09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name PortletCo
nfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not have a matc
hing entry in liferay-portlet.xml
09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name WSRP4JPor
tletB_WAR_wsrp4jproxyportlet is described in portlet.xml but does not have a mat
ching entry in liferay-portlet.xml
09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name WSRP4JPor
tletA_WAR_wsrp4jproxyportlet is described in portlet.xml but does not have a mat
ching entry in liferay-portlet.xml
09:11:01,833 ERROR [HotDeployUtil:52] com.liferay.portal.kernel.deploy.HotDeploy
Exception: Error registering portlets for wsrp4j-proxyportlet
at com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
ployPortletListener.java:348)
at com.liferay.portal.kernel.deploy.HotDeployUtil._fireDeployEvent(HotDe
ployUtil.java:86)
at com.liferay.portal.kernel.deploy.HotDeployUtil.fireDeployEvent(HotDep
loyUtil.java:43)
at com.liferay.portal.kernel.servlet.PortletContextListener.contextIniti
alized(PortletContextListener.java:41)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
t.java:3729)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
187)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
9)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.jav
a:904)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
ava:867)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474
)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:292)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:119)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBas
e.java:1305)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1569)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1578)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
un(ContainerBase.java:1558)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException:
org.apache.wsrp4j.consumer.configportlet.controller.ProducerRegistry
ConfigPortlet
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1352)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1198)
at com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
ployPortletListener.java:151)
... 19 more
Regards,
Kevin
Re: Re[2]: Proxy Portlet
Posted by Kevin Irmscher <ke...@gmail.com>.
I've already deployed own portlets without any problems. I'm using the
admin portlet of the portal for deployment. Liferay is kind of
sensitive to the settings in the web.xml and portlet.xml. There might
be some incompatibilities. I'll keep trying and post a solution if I
can find one.
Regards,
Kevin
On 2/1/07, Sandy Pérez González <sp...@yahoo.es> wrote:
> Try to deploy a JSR168-compliant portlet, which is not
> included into Liferay's installation, you can use one
> of these http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/portletsamples.war
>
> If you achieve to deploy it, you would follow the same steps
> for the Proxy portlet. This is an advice.
>
> Regards
> Sandy
>
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
>
> > Kevin Irmscher escribió:
> >> On 1/31/07, Diego Louzán <dl...@apache.org> wrote:
> >> Kevin Irmscher escribió:
> >>> Hi!
> >>
> >>> Is the Consumer Proxy Portlet coming with WSRP4J JSR 168 compliant or
> >>> is it customized for the Pluto portal. I tried to deploy it to the
> >>> Liferay portal and to the Exo portlet container but neither of them
> >>> did work. Do you plan to make the Proxy Portlet work with other
> >>> containers or do you focus on Pluto?
> >>
> >>> Regards,
> >>> Kevin
> >>
> >> The ProxyPortlet is JSR-168 compliant, in fact we have just made it
> >> independent from Pluto. If you include the exception you are getting
> >> maybe we can help you. As long as you don't use the Producer Templates,
> >> which are portal-dependent, you should be able to deploy the portlet on
> >> any portal.
> >>
> >> Regards.
> >> Diego.
> >>>
>
> >> I tried to deploy wsrp4j-proxyportlet.war to Liferay 4.2.1 portal and
> >> get the following exception:
>
> >> 09:10:58,507 INFO [AutoDeployPortletListener:88] Portlets for
> >> \home\liferay\deploy\wsrp4j-proxyportlet.war copied successfully
> >> 09:11:01,813 INFO [HotDeployPortletListener:129] Registering portlets
> >> for wsrp4
> >> j-proxyportlet
> >> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> >> ProducerC
> >> onfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> >> have a mat
> >> ching entry in liferay-portlet.xml
> >> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> >> PortletCo
> >> nfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> >> have a matc
> >> hing entry in liferay-portlet.xml
> >> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> >> WSRP4JPor
> >> tletB_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> >> have a mat
> >> ching entry in liferay-portlet.xml
> >> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> >> WSRP4JPor
> >> tletA_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> >> have a mat
> >> ching entry in liferay-portlet.xml
> >> 09:11:01,833 ERROR [HotDeployUtil:52]
> >> com.liferay.portal.kernel.deploy.HotDeploy
> >> Exception: Error registering portlets for wsrp4j-proxyportlet
> >> at
> >> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
> >> ployPortletListener.java:348)
> >> at
> >> com.liferay.portal.kernel.deploy.HotDeployUtil._fireDeployEvent(HotDe
> >> ployUtil.java:86)
> >> at
> >> com.liferay.portal.kernel.deploy.HotDeployUtil.fireDeployEvent(HotDep
> >> loyUtil.java:43)
> >> at
> >> com.liferay.portal.kernel.servlet.PortletContextListener.contextIniti
> >> alized(PortletContextListener.java:41)
> >> at
> >> org.apache.catalina.core.StandardContext.listenerStart(StandardContex
> >> t.java:3729)
> >> at
> >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4
> >> 187)
> >> at
> >> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
> >> .java:759)
> >> at
> >> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
> >> 9)
> >> at
> >> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
>
> >> at
> >> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.jav
> >> a:904)
> >> at
> >> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
> >> ava:867)
> >> at
> >> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474
> >> )
> >> at
> >> org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190)
> >> at
> >> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
> >> :292)
> >> at
> >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
> >> eSupport.java:119)
> >> at
> >> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBas
> >> e.java:1305)
> >> at
> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
> >> rocessChildren(ContainerBase.java:1569)
> >> at
> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
> >> rocessChildren(ContainerBase.java:1578)
> >> at
> >> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
> >> un(ContainerBase.java:1558)
> >> at java.lang.Thread.run(Thread.java:595)
> >> Caused by: java.lang.ClassNotFoundException:
>
> >> org.apache.wsrp4j.consumer.configportlet.controller.ProducerRegistry
> >> ConfigPortlet
> >> at
> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> >> der.java:1352)
> >> at
> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> >> der.java:1198)
> >> at
> >> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
> >> ployPortletListener.java:151)
> >> ... 19 more
>
> >> Regards,
> >> Kevin
>
> > With only that info, it seems a configuration problem with Liferay. It
> > complains about all the four portlets included in ProxyPortlet not being
> > included in the configuration file liferay-portlet.xml. I've never used
> > Liferay so maybe I'm wrong, but that seems like a portal configuration
> > problem, not a ProxyPortlet problem. You'll have to check Liferay
> > documentation & logs to find out exactly what's the problem.
>
> > Regards.
> > Diego.
>
>
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.3 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> > iD8DBQFFwcGygyzZYflJelERAunHAKCCO8TrKRDjm8UhAYnwj+nXs/k+4ACeK+R9
> > RUe+SRZzLUmiXpUe9lDwMKI=
> > =S5AA
> > -----END PGP SIGNATURE-----
>
>
Re[2]: Proxy Portlet
Posted by Sandy Pérez González <sp...@yahoo.es>.
Try to deploy a JSR168-compliant portlet, which is not
included into Liferay’s installation, you can use one
of these http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/portletsamples.war
If you achieve to deploy it, you would follow the same steps
for the Proxy portlet. This is an advice.
Regards
Sandy
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Kevin Irmscher escribió:
>> On 1/31/07, Diego Louzán <dl...@apache.org> wrote:
>> Kevin Irmscher escribió:
>>> Hi!
>>
>>> Is the Consumer Proxy Portlet coming with WSRP4J JSR 168 compliant or
>>> is it customized for the Pluto portal. I tried to deploy it to the
>>> Liferay portal and to the Exo portlet container but neither of them
>>> did work. Do you plan to make the Proxy Portlet work with other
>>> containers or do you focus on Pluto?
>>
>>> Regards,
>>> Kevin
>>
>> The ProxyPortlet is JSR-168 compliant, in fact we have just made it
>> independent from Pluto. If you include the exception you are getting
>> maybe we can help you. As long as you don't use the Producer Templates,
>> which are portal-dependent, you should be able to deploy the portlet on
>> any portal.
>>
>> Regards.
>> Diego.
>>>
>> I tried to deploy wsrp4j-proxyportlet.war to Liferay 4.2.1 portal and
>> get the following exception:
>> 09:10:58,507 INFO [AutoDeployPortletListener:88] Portlets for
>> \home\liferay\deploy\wsrp4j-proxyportlet.war copied successfully
>> 09:11:01,813 INFO [HotDeployPortletListener:129] Registering portlets
>> for wsrp4
>> j-proxyportlet
>> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
>> ProducerC
>> onfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
>> have a mat
>> ching entry in liferay-portlet.xml
>> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
>> PortletCo
>> nfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
>> have a matc
>> hing entry in liferay-portlet.xml
>> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
>> WSRP4JPor
>> tletB_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
>> have a mat
>> ching entry in liferay-portlet.xml
>> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
>> WSRP4JPor
>> tletA_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
>> have a mat
>> ching entry in liferay-portlet.xml
>> 09:11:01,833 ERROR [HotDeployUtil:52]
>> com.liferay.portal.kernel.deploy.HotDeploy
>> Exception: Error registering portlets for wsrp4j-proxyportlet
>> at
>> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
>> ployPortletListener.java:348)
>> at
>> com.liferay.portal.kernel.deploy.HotDeployUtil._fireDeployEvent(HotDe
>> ployUtil.java:86)
>> at
>> com.liferay.portal.kernel.deploy.HotDeployUtil.fireDeployEvent(HotDep
>> loyUtil.java:43)
>> at
>> com.liferay.portal.kernel.servlet.PortletContextListener.contextIniti
>> alized(PortletContextListener.java:41)
>> at
>> org.apache.catalina.core.StandardContext.listenerStart(StandardContex
>> t.java:3729)
>> at
>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4
>> 187)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
>> .java:759)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
>> 9)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.jav
>> a:904)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
>> ava:867)
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474
>> )
>> at
>> org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190)
>> at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
>> :292)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
>> eSupport.java:119)
>> at
>> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBas
>> e.java:1305)
>> at
>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
>> rocessChildren(ContainerBase.java:1569)
>> at
>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
>> rocessChildren(ContainerBase.java:1578)
>> at
>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
>> un(ContainerBase.java:1558)
>> at java.lang.Thread.run(Thread.java:595)
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.wsrp4j.consumer.configportlet.controller.ProducerRegistry
>> ConfigPortlet
>> at
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
>> der.java:1352)
>> at
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
>> der.java:1198)
>> at
>> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
>> ployPortletListener.java:151)
>> ... 19 more
>> Regards,
>> Kevin
> With only that info, it seems a configuration problem with Liferay. It
> complains about all the four portlets included in ProxyPortlet not being
> included in the configuration file liferay-portlet.xml. I've never used
> Liferay so maybe I'm wrong, but that seems like a portal configuration
> problem, not a ProxyPortlet problem. You'll have to check Liferay
> documentation & logs to find out exactly what's the problem.
> Regards.
> Diego.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> iD8DBQFFwcGygyzZYflJelERAunHAKCCO8TrKRDjm8UhAYnwj+nXs/k+4ACeK+R9
> RUe+SRZzLUmiXpUe9lDwMKI=
> =S5AA
> -----END PGP SIGNATURE-----
Re: Proxy Portlet
Posted by Diego Louzán <dl...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevin Irmscher escribió:
> On 1/31/07, Diego Louzán <dl...@apache.org> wrote:
> Kevin Irmscher escribió:
>> Hi!
>
>> Is the Consumer Proxy Portlet coming with WSRP4J JSR 168 compliant or
>> is it customized for the Pluto portal. I tried to deploy it to the
>> Liferay portal and to the Exo portlet container but neither of them
>> did work. Do you plan to make the Proxy Portlet work with other
>> containers or do you focus on Pluto?
>
>> Regards,
>> Kevin
>
> The ProxyPortlet is JSR-168 compliant, in fact we have just made it
> independent from Pluto. If you include the exception you are getting
> maybe we can help you. As long as you don't use the Producer Templates,
> which are portal-dependent, you should be able to deploy the portlet on
> any portal.
>
> Regards.
> Diego.
>>
> I tried to deploy wsrp4j-proxyportlet.war to Liferay 4.2.1 portal and
> get the following exception:
> 09:10:58,507 INFO [AutoDeployPortletListener:88] Portlets for
> \home\liferay\deploy\wsrp4j-proxyportlet.war copied successfully
> 09:11:01,813 INFO [HotDeployPortletListener:129] Registering portlets
> for wsrp4
> j-proxyportlet
> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> ProducerC
> onfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> have a mat
> ching entry in liferay-portlet.xml
> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> PortletCo
> nfig_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> have a matc
> hing entry in liferay-portlet.xml
> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> WSRP4JPor
> tletB_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> have a mat
> ching entry in liferay-portlet.xml
> 09:11:01,833 ERROR [PortletLocalServiceImpl:302] Portlet with the name
> WSRP4JPor
> tletA_WAR_wsrp4jproxyportlet is described in portlet.xml but does not
> have a mat
> ching entry in liferay-portlet.xml
> 09:11:01,833 ERROR [HotDeployUtil:52]
> com.liferay.portal.kernel.deploy.HotDeploy
> Exception: Error registering portlets for wsrp4j-proxyportlet
> at
> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
> ployPortletListener.java:348)
> at
> com.liferay.portal.kernel.deploy.HotDeployUtil._fireDeployEvent(HotDe
> ployUtil.java:86)
> at
> com.liferay.portal.kernel.deploy.HotDeployUtil.fireDeployEvent(HotDep
> loyUtil.java:43)
> at
> com.liferay.portal.kernel.servlet.PortletContextListener.contextIniti
> alized(PortletContextListener.java:41)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContex
> t.java:3729)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4
> 187)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
> .java:759)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
> 9)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.jav
> a:904)
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
> ava:867)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474
> )
> at
> org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
> :292)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
> eSupport.java:119)
> at
> org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBas
> e.java:1305)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
> rocessChildren(ContainerBase.java:1569)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
> rocessChildren(ContainerBase.java:1578)
> at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
> un(ContainerBase.java:1558)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.wsrp4j.consumer.configportlet.controller.ProducerRegistry
> ConfigPortlet
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> der.java:1352)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
> der.java:1198)
> at
> com.liferay.portal.deploy.HotDeployPortletListener.invokeDeploy(HotDe
> ployPortletListener.java:151)
> ... 19 more
> Regards,
> Kevin
With only that info, it seems a configuration problem with Liferay. It
complains about all the four portlets included in ProxyPortlet not being
included in the configuration file liferay-portlet.xml. I've never used
Liferay so maybe I'm wrong, but that seems like a portal configuration
problem, not a ProxyPortlet problem. You'll have to check Liferay
documentation & logs to find out exactly what's the problem.
Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFwcGygyzZYflJelERAunHAKCCO8TrKRDjm8UhAYnwj+nXs/k+4ACeK+R9
RUe+SRZzLUmiXpUe9lDwMKI=
=S5AA
-----END PGP SIGNATURE-----