I moved the dependencies into the parent pom (and inserted a parent-element into the block pom). I added the runmode-parameter to the tomcat startscript. I checked the versions, though they were ok (had seen this issues in earlier postings). Unfortunately, flow on tomcat still doesn't work (but works on jetty).
Thanks anyway for having looked into it! Jens > > Did you change the version of your cocoon block to 1.0.0 because I think by > default it > generates 1.0-SNAPSHOT. And you declare version 1.0.0 as a dependency. > > Robby > > -----Original Message----- > From: Jens Reufsteck [mailto:jens.reufst...@staufenbiel.de] > Sent: Monday, March 08, 2010 1:41 PM > To: users@cocoon.apache.org > Subject: RE: tutorial example work with jetty but not on tomcat6 > > > Maybe you can copy paste your dependencies and also the relevant snippets > > from your > > block-servlet-service.xml? > > > > This is the parent pom.xml > > <project xmlns="http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > > <modelVersion>4.0.0</modelVersion> > <packaging>pom</packaging> > > <groupId>gti.ffm</groupId> > <artifactId>getting-started</artifactId> > <version>1.0.0</version> > > <name>Getting started</name> > > <modules> > <module>testApp</module> > <module>samples</module> > </modules> > </project> > > These are the dependencies of the webapps pom.xml > > <dependencies> > <dependency> > <groupId>gti.ffm</groupId> > <artifactId>samples</artifactId> > <version>1.0.0</version> > </dependency> > </dependencies> > > And these are the dependencies in the pom.xml of the first (and only) block: > > <dependencies> > <dependency> > <groupId>org.apache.cocoon</groupId> > <artifactId>cocoon-core</artifactId> > <version>2.2.0</version> > </dependency> > <dependency> > <groupId>org.apache.cocoon</groupId> > <artifactId>cocoon-servlet-service-components</artifactId> > <version>1.0.0</version> > </dependency> > <dependency> > <groupId>org.apache.cocoon</groupId> > <artifactId>cocoon-template-impl</artifactId> > <version>1.1.0</version> > </dependency> > <dependency> > <groupId>org.apache.cocoon</groupId> > <artifactId>cocoon-flowscript-impl</artifactId> > <version>1.0.0</version> > </dependency> > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > <version>2.4</version> > <scope>provided</scope> > </dependency> > </dependencies> > > And here is the block-servlet-service.xml: > > <beans xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:servlet="http://cocoon.apache.org/schema/servlet"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.5.xsd > http://cocoon.apache.org/schema/servlet > http://cocoon.apache.org/schema/servlet/cocoon-servlet-1.0.xsd";> > > <bean name="gti.ffm.samples.service" > class="org.apache.cocoon.sitemap.SitemapServlet"> > <servlet:context mount-path="/samples" > context-path="blockcontext:/samples/"/> > </bean> > > </beans> > > Apart from the parent pom and the dependency in the webapps pom everything is > just as it > came out of the archetypes. > > Many thanks! > Jens > > > > > > Kind regards, > > Robby Pelssers > > > > -----Original Message----- > > From: Jens Reufsteck [mailto:jens.reufst...@staufenbiel.de] > > Sent: Monday, March 08, 2010 11:54 AM > > To: users@cocoon.apache.org; Jens Reufsteck > > Subject: RE: tutorial example work with jetty but not on tomcat6 > > > > I tried to dig deeper into the problem, but I'm really stuck. > > > > Am Donnerstag, 4. März 2010 14:58:41 schrieben Sie: > > > I've just started with Cocoon 2.2 (after using Cocoon 2.1 successfully for > > > many years). > > > > > > I'm following the tutorials, i.e. I'm using mvn (2.2.1) having installed > > > the webapp plus an example block. > > > > > > Everything's fine with jetty (mvn jetty:run out of the webapp directory). > > > On tomcat I'm getting the following Exception: > > > > > > > What I found is: > > > > Everything works fine without flowscript. As soon as I've got the map:flow > > element in the sitemap, I get the error message as passed earlier. > > > > > 2010-03-04 13:50:30,826 ERROR http-8080-1 cocoon.access - Internal Cocoon > > > Problem > > > org.apache.avalon.framework.service.ServiceException: Exception during > > > lookup of component with > > > 'org.apache.cocoon.components.flow.Interpreter/javascript'. > > > (Key='AvalonServiceManager') > > > at > > > org.apache.cocoon.core.container.spring.avalon.AvalonServiceManager.lookup( > > > AvalonServiceManager.java:63) > > > > > > ... > > > > > > Caused by: org.springframework.beans.factory.BeanCreationException: Error > > > creating bean with name > > > 'org.apache.cocoon.components.flow.Interpreter/javascript': Initialization > > > of bean failed; nested exception is > > > org.springframework.beans.factory.BeanCreationException: Unable to > > > initialize Avalon component with role > > > org.apache.cocoon.components.flow.Interpreter/javascript; nested exception > > > is java.lang.NullPointerException > > > at > > > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactor > > > y.doCreateBean(AbstractAutowireCapableBeanFactory.java:445) > > > > > > ... > > > > The catalina.out log says: > > > > FATAL Servlet.service() for servlet DispatcherServlet threw exception > > java.lang.NullPointerException > > > > > > And when starting tomcat I find the following in the logs: > > > > INFO 2010-03-08 09:49:32,776 [main] > > org.springframework.web.context.support.XmlWebApplicationContext - Bean > > 'org.apache.avalon.framework.context.Context' is not eligible for getting > > processed by all BeanPostProcessors (for example: not eligible for auto- > > proxying) > > INFO 2010-03-08 09:49:32,777 [main] > > org.springframework.web.context.support.XmlWebApplicationContext - Bean > > 'org.apache.avalon.framework.context.Context' is not eligible for getting > > processed by all BeanPostProcessors (for example: not eligible for auto- > > proxying) > > INFO 2010-03-08 09:49:32,778 [main] > > org.springframework.web.context.support.XmlWebApplicationContext - Bean > > 'org.apache.cocoon.core.container.spring.avalon.ConfigurationInfo' is not > > eligible for getting processed by all BeanPostProcessors (for example: not > > eligible for auto-proxying) > > INFO 2010-03-08 09:49:32,778 [main] > > org.springframework.web.context.support.XmlWebApplicationContext - Bean > > 'org.apache.cocoon.core.container.spring.avalon.ConfigurationInfo' is not > > eligible for getting processed by all BeanPostProcessors (for example: not > > eligible for auto-proxying) > > > > No idea, if this is related. > > > > Sorry, I'm new to Cocoon 2.2, I'm newbie with maven, i'm newbie with spring, > > and I'm not expert with tomcat. > > > > Any help is much appreciated! > > Jens Reufsteck > > > > -- > > Jens Reufsteck > > Marketing & Online Director > > > > Staufenbiel GmbH > > Events & Recruiting Solutions > > (bisher Hobsons GmbH) > > > > Wildunger Straße 6, 60487 Frankfurt am Main > > www.staufenbiel.de www.hobsons.de www.groupgti.com > > > > Tel.: +49 (069) 25537-140 > > Fax: +49 (069) 25537-2140 > > > > > > Geschäftsführer: Judith Oppitz, Birgit Giesen, Graham Storey, Martin > > Halliday > > Amtsgericht Frankfurt HRB 58610 > > > > Internet communications are not secure and therefore Staufenbiel GmbH does > > not accept > > legal responsibility > > for the contents of this message. Any views or opinions presented are > > solely those of the > > author and do not > > necessarily represent those of Staufenbiel GmbH unless otherwise > > specifically stated. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > > For additional commands, e-mail: users-h...@cocoon.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > For additional commands, e-mail: users-h...@cocoon.apache.org
