cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JLe <my-own-em...@trashymail.com>
Subject Re: Migrating Cocoon 2.1 project to Cocoon 2.2
Date Mon, 28 Jul 2008 08:16:48 GMT

Is it possible to just copy my 2.1 application into the
src\main\resources\COB-INF folder of 2.2?
or is there an other directory?



Barbara Slupik-3 wrote:
> 
> In cocoon-2.2 everything runs as blocks. So you have to put your old  
> application into one or more blocks and create cocoon-2.2 application  
> to run them. There are some changes which are described Migration  
> guide, for example for cforms go to cocoon page, Blocks 2.2/Forms/ 
> Migration guide and follow the instruction.
> 
> Now I use maven/jetty in my development environment because this  
> allows to see changes in cforms, css, sitemap, flow, etc immediately  
> after refreshing the screen. My test and production environment runs  
> with tomcat.
> 
> 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 my 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. Put cocoon-webapp-1.0.war file in my tomcat/webapps and start the  
> application with url similar to this
> 
> http://localhost:8080/cocoon-webapp-1.0/myBlock/
> 
> 
> Barbara
> 
> On 25 Jul, 2008, at 11:06 am, JLe wrote:
> 
>>
>> Hi all,
>>
>> I have an existing Cocoon application written under cocoon 2.1 (old  
>> version)
>> now, after the release of 2.2.0 i am going to "upgrade" my  
>> application to
>> the new cocoon release because of performance reasons.
>> Does anyone already have experience doing this? - are there some  
>> special
>> things being aware of, some things to note?
>>
>> Thanks in advance...
>> -- 
>> View this message in context: http://www.nabble.com/Migrating- 
>> Cocoon-2.1-project-to-Cocoon-2.2-tp18648820p18648820.html
>> Sent from the Cocoon - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Migrating-Cocoon-2.1-project-to-Cocoon-2.2-tp18648820p18685946.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message