I use maven/jetty in my development environment and tomcat for test/ production. I build cocoon-2.2 application like this:

1. Create block myBlock

cd /.../cocoon-2.2.0
mvn archetype:create -DarchetypeGroupId=org.apache.cocoon - DarchetypeArtifactId=cocoon-22-archetype-block - DarchetypeVersion=1.0.0 -DgroupId=my.domain -DartifactId=myBlock


2. Test myBlock in maven/jetty

cd /.../cocoon-2.2.0/myBlock
mvn jetty:run

http://localhost:8888/myBlock/


3. Build myBlock jar file and update maven repository. I assume that version number is 1.0, version number is defined in myBlock pom file

cd /.../cocoon-2.2.0/myBlock
mvn package

mvn install:install-file -DgroupId=my.domain -DartifactId=myBlock - Dversion=1.0 -Dpackaging=jar -Dfile=target/myBlock-1.0.jar


4. Create cocoon web application cocoon-webapp

cd /.../cocoon-2.2.0
mvn archetype:create -DarchetypeGroupId=org.apache.cocoon - DarchetypeArtifactId=cocoon-22-archetype-webapp - DarchetypeVersion=1.0.0 -DgroupId=my.domain -DartifactId=cocoon-webapp


5. Add myBlock (all application blocks) to cocoon-webapp pom file

    <dependency>
      <groupId>my.domain</groupId>
      <artifactId>myBlock</artifactId>
      <version>1.0</version>
    </dependency>


6. Package cocoon-webapp. This will create cocoon-webapp-1.0.war file

cd /.../cocoon-2.2.0/cocoon-webapp
mvn package


7. Test cocoon-webapp in maven/jetty

cd /.../cocoon-2.2.0/cocoon-webapp
mvn jetty:run

http://localhost:8888/myBlock/


8. Put cocoon-webapp-1.0.war file in tomcat/webapps and start the application with url similar to this

http://localhost:8080/cocoon-webapp-1.0/myBlock/


Barbara


On 14 Jul, 2008, at 9:29 am, Robby Pelssers wrote:

Well, since I am still facing the same problem I did a thorough search on the internet and I noticed I was not the only one having this problem:



http://carlback.blogspot.com/2007/03/apex-cocoon-pdf-and-more.html (number 13)



http://www.nabble.com/Build-2.1.8-with-Java-1.5- td2181360.html#a2182531



http://www.nabble.com/Installation-problem-td12611184.html#a12612781





Here a little article about the problem called “Buggy MemoryMapping in the JDK”

http://www.theresearchkitchen.com/blog/archives/date/2005/05







And here the complete discussion on the website of sun:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4724038







I haven’t found any real good workarounds so I am glad to hear any proposals.



Cheers,

Robby
















Reply via email to