It's quite easy and if you read http://cocoon.apache.org/1370_1_1.html (getting started) you should be able to follow what's going on.
When you talk about war.. you mean creating a cocoon-archetype-webapp by running mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org and selecting option 3. Then you get following structure: mywebapproject -src -main -resources -webapp -WEB-INF -applicationContext.xml -log4j.xml -web.xml If you had selected option 2 or 1, you would have gotten the structure like you mentioned. But the packaging of such a project is 'jar' like mentioned earlier in the thread. So typically, that jar would go into the WEB-INF/lib folder if you declare a dependency in 'mywebappproject' on that cocoon block. Hope that helps a bit. Cheers, Robby Pelssers -----Original Message----- From: Ivan Latysh [mailto:[email protected]] Sent: Sunday, May 31, 2009 12:32 AM To: [email protected] Subject: Re: Webapp structure Mansour Al Akeel wrote: [skipped] > Since you have a directory called COB-INF, I would say this is a cocoon > block. These are directories from a simple webapp that suppose to have a single cocoon (exploded) module. > Check this: http://wiki.apache.org/cocoon/BlocksDefinition Thank you, checked the page, it talks about a cocoon block structure, and say nothing about a webapp, or a deployment options. Can anybody share a simple `hello world` war with a single cocoon module ? >> ======================= >> WEB-INF >> + classes >> | + com >> | + COB-INF >> | | + demo >> | | + spring-bean.jx.xml >> | | + welcome.xml >> | + META-INF >> | + cocoon >> | + spring >> | + block-servlet-service.xml >> | + demo-application-context.xml >> + lib >> + applicationContext.xml >> + log4j.xml >> + web.xml >> index.jsp >> ======================= -- Ivan Latysh [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
