portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gonzalo Aguilar Delgado <gagui...@aguilardelgado.com>
Subject Re: Having problem with portlet deployment [SOLVED]
Date Mon, 18 Jan 2010 18:16:21 GMT
Hi Woonsan, 

It was the portlet-api that was deployed as jar instead of be provided
by environment due to an error in the pom.xml

It was resolved.

Note the provided header:
>             org.apache.portals

> >             portlet-api_2.0_spec
> >             ${portals.portlet2-api-spec.version}
> >             jar
> >             provided 



El lun, 18-01-2010 a las 02:00 -0800, Woonsan Ko escribió:

> Hi Gonzalo,
> 
> If it displays the message, "Cannot create Portlet instance ...", then there must be
some error logs in jetspeed.log file.
> I'm seeing these lines in JetspeedPortletFactory.java:
> 
>                 catch (Exception e)
>                 {
>                     String msg = "Cannot create Portlet instance " + pd.getPortletClass()
+ " for Portlet Application " + paName;                        
>                     log.error(msg, e);
>                     throw new UnavailableException(msg);
>                 }
> 
> 
> Regards,
> 
> Woonsan
> 
> 
> 
> ----- Original Message ----
> > From: Gonzalo Aguilar Delgado <gaguilar@aguilardelgado.com>
> > To: Jetspeed Developers List <jetspeed-dev@portals.apache.org>
> > Sent: Sat, January 16, 2010 1:53:52 PM
> > Subject: Re: Having problem with portlet deployment [SOLVED]
> > 
> > Hi all, 
> > It seems that I included the portlet-api and forgot to add the scope =
> > provided...
> > 
> > This caused every portlet built to fail silently... It initialized, it
> > loaded and stoped to work silently with the only error "Cannot create
> > Portlet instance..."
> > 
> > No debug trace, no nothing. So guys, be carefull with this, I spent a
> > lot of time debuging this... Maybe I'm not so smart...
> > 
> > 
> > This is main config I have now:
> >                  
> >             org.apache.portals
> >             portlet-api_2.0_spec
> >             ${portals.portlet2-api-spec.version}
> >             jar
> >             provided 
> >         
> >         
> >             portals-bridges-common
> >             org.apache.portals.bridges
> >             ${org.apache.portals.bridges.common.version}
> >             provided
> >         
> >         
> >             javax.servlet
> >             servlet-api
> >             ${servlet-api.version}
> >             jar
> >             provided
> >         
> > 
> > El jue, 14-01-2010 a las 19:15 +0100, Gonzalo Aguilar Delgado escribió:
> > 
> > > Hi, 
> > > 
> > > This one was my fault. I forgot to add the portlet.xml file. 
> > > 
> > > Now I added it and it does not crash... (Should Jetspeed warn instead of
> > > crash?)
> > > 
> > > Here is the definition
> > > ---------------------
> > > 
> > >         Contact Status Portlet
> > >         crm-survey-show
> > >         L2 CRM Customer Status
> > > 
> > > 
> > com.level2.portals.crm.wicket.contact.portlets.ContactStatusPortlet
> > >         
> > >             wicketFilterPath
> > >             /crm-contact-status
> > >         
> > > 
> > >         
> > >             */*
> > >             VIEW
> > >         
> > >         es
> > >         
> > >             L2 CRM Customer Status
> > >             >L2 CRM Customer Status
> > >             L2crm
> > >         
> > >         
> > >     
> > > ----------------------
> > > 
> > > But the portlet now shows:
> > > 
> > >   Cannot create Portlet instance
> > > com.level2.portals.crm.wicket.contact.portlets.ContactStatusPortlet for
> > > Portlet Application crm-contact
> > > 
> > > I debugged it and the class is almost empty. Only constructor that got
> > > called without errors. But even with that it failed to start...
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > El jue, 14-01-2010 a las 12:23 +0100, Gonzalo Aguilar Delgado escribió:
> > > 
> > > > I forgot to add portlet configuration:
> > > > 
> > > > web.xml 
> > > > ---------------------
> > > > 
> > > >     
> > > >     
> > > >         contactStatusPortlet
> > > > 
> > > > org.apache.wicket.protocol.http.WicketFilter
> > > >         
> > > >             applicationFactoryClassName
> > > > 
> > > > 
> > org.apache.wicket.spring.SpringWebApplicationFactory
> > > >         
> > > >         
> > > >             applicationBean
> > > >             contactStatusPortletBean
> > > >         
> > > >     
> > > >     
> > > >         contactStatusPortlet
> > > >         /crm-contact-status/*
> > > >         REQUEST
> > > >         INCLUDE
> > > >         FORWARD
> > > >     
> > > > 
> > > > portlet-beans.xml
> > > > ---------------------------
> > > > 
> > > > 
> > > >     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> > > >     xmlns:tx="http://www.springframework.org/schema/tx"
> > > >     xmlns:aop="http://www.springframework.org/schema/aop"
> > > >     xsi:schemaLocation="http://www.springframework.org/schema/beans
> > > >         http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
> > > >        http://www.springframework.org/schema/tx
> > > > http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
> > > >        http://www.springframework.org/schema/aop
> > > > http://www.springframework.org/schema/aop/spring-aop-2.5.xsd">
> > > > 
> > > >     
> > > >     
> > > > 
> > class="com.level2crm.portals.crm.wicket.contact.WicketContactStatusApplication"/>
> > > >     
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > El jue, 14-01-2010 a las 12:06 +0100, Gonzalo Aguilar Delgado escribió:
> > > > 
> > > > > Hi 
> > > > > 
> > > > > I spent last weeks recoding my system to adapt it to jetspeed 2.2.1
and
> > > > > apache project organization.
> > > > > 
> > > > > But I found that with lasts updates none of my portlets work.  They
are
> > > > > built on Spring, Wicket and Jetspeed.
> > > > > 
> > > > > Every portlet shows a similar message.
> > > > > 
> > > > > GRAVE: JetspeedContainerServlet: initialization failed for Portlet
> > > > > Application at: /crm-contact
> > > > > org.apache.jetspeed.components.portletregistry.RegistryException:
Error
> > > > > starting portlet application crm-contact
> > > > >     at
> > > > > 
> > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.attemptStartPA(PortletApplicationManager.java:683)
> > > > >     at
> > > > > 
> > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.tryStartPortletApplication(PortletApplicationManager.java:244)
> > > > >     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > >     at
> > > > > 
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > > > >     at
> > > > > 
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > > >     at java.lang.reflect.Method.invoke(Method.java:616)
> > > > >     at
> > > > > 
> > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
> > > > >     at
> > > > > 
> > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
> > > > >     at
> > > > > 
> > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
> > > > >     at
> > > > > 
> > org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
> > > > >     at
> > > > > 
> > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
> > > > >     at
> > > > > 
> > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> > > > >     at $Proxy34.tryStartPortletApplication(Unknown Source)
> > > > >     at
> > > > > 
> > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.retryStartPortletApplication(PortletApplicationManager.java:214)
> > > > >     at
> > > > > 
> > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.startPortletApplication(PortletApplicationManager.java:195)
> > > > >     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > >     at
> > > > > 
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> > > > >     at
> > > > > 
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > > > >     at java.lang.reflect.Method.invoke(Method.java:616)
> > > > >     at
> > > > > 
> > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
> > > > >     at
> > > > > 
> > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
> > > > >     at $Proxy34.startPortletApplication(Unknown Source)
> > > > >     at
> > > > > 
> > org.apache.jetspeed.container.JetspeedContainerServlet.attemptStart(JetspeedContainerServlet.java:204)
> > > > >     at org.apache.jetspeed.container.JetspeedContainerServlet
> > > > > $1.run(JetspeedContainerServlet.java:170)
> > > > >     at java.util.TimerThread.mainLoop(Timer.java:534)
> > > > >     at java.util.TimerThread.run(Timer.java:484)
> > > > > 
> > > > > What can it be?
> > > > > 
> > > > > 
> 
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message