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 Sat, 16 Jan 2010 12:53:52 GMT
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:
             	<dependency>
			<groupId>org.apache.portals</groupId>
			<artifactId>portlet-api_2.0_spec</artifactId>
			<version>${portals.portlet2-api-spec.version}</version>
			<type>jar</type>
			<scope>provided</scope> <!-- This caused everything to fail, it was
previously absent and messed everything!!! -->
		</dependency>
		<dependency>
			<artifactId>portals-bridges-common</artifactId>
			<groupId>org.apache.portals.bridges</groupId>
			<version>${org.apache.portals.bridges.common.version}</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupId>javax.servlet</groupId>
			<artifactId>servlet-api</artifactId>
			<version>${servlet-api.version}</version>
			<type>jar</type>
			<scope>provided</scope>
		</dependency>

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
> ---------------------
> <portlet>
> 		<description>Contact Status Portlet</description>
> 		<portlet-name>crm-survey-show</portlet-name>
> 		<display-name>L2 CRM Customer Status</display-name>
> 
> <portlet-class>com.level2.portals.crm.wicket.contact.portlets.ContactStatusPortlet</portlet-class>
> 		<init-param>
> 			<name>wicketFilterPath</name>
> 			<value>/crm-contact-status</value>
> 		</init-param>
> 
> 		<supports>
> 			<mime-type>*/*</mime-type>
> 			<portlet-mode>VIEW</portlet-mode>
> 		</supports>
> 		<supported-locale>es</supported-locale>
> 		<portlet-info>
> 			<title>L2 CRM Customer Status</title>
> 			<short-title>>L2 CRM Customer Status</short-title>
> 			<keywords>L2crm</keywords>
> 		</portlet-info>
> 		<!--
> <supported-public-render-parameter>crmportal:userId</supported-public-render-parameter>
-->
> 	</portlet>
> ----------------------
> 
> 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 
> > ---------------------
> > 
> > 	<!-- Wicket filters -->
> > 	<filter>
> > 		<filter-name>contactStatusPortlet</filter-name>
> > 
> > <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
> > 		<init-param>
> > 			<param-name>applicationFactoryClassName</param-name>
> > 
> > <param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
> > 		</init-param>
> > 		<init-param>
> > 			<param-name>applicationBean</param-name>
> > 			<param-value>contactStatusPortletBean</param-value>
> > 		</init-param>
> > 	</filter>
> > 	<filter-mapping>
> > 		<filter-name>contactStatusPortlet</filter-name>
> > 		<url-pattern>/crm-contact-status/*</url-pattern>
> > 		<dispatcher>REQUEST</dispatcher>
> > 		<dispatcher>INCLUDE</dispatcher>
> > 		<dispatcher>FORWARD</dispatcher>
> > 	</filter-mapping>
> > 
> > portlet-beans.xml
> > ---------------------------
> > <?xml version="1.0" encoding="UTF-8"?>
> > <beans xmlns="http://www.springframework.org/schema/beans"
> > 	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">
> > 
> > 	<!-- setup wicket application -->
> > 	<bean id="contactStatusPortletBean"
> > class="com.level2crm.portals.crm.wicket.contact.WicketContactStatusApplication"/>
> > 	
> > </beans>
> > 
> > 
> > 
> > 
> > 
> > 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?
> > > 
> > > 

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