Re: Explanation of the Cocoon directory structure
Dev at weitling wrote: Hi! The Cocoon directory structure isn't very concise: many directories with the same or at least similar names at different locations, some directories with non-intuitive names (e.g. lib/endorsed: why endorsed?). If there's a problem I don't know where to look, I don't know where to place my files, I don't know which parts are superfluous and and and... Are docs about that anywhere in the outside world without having to pay $ 30 for an outdated book? which cocoon version are you refering to ? -- Leszek Gawron, IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Explanation of the Cocoon directory structure
Hi Florian, On 13.09.2006 23:27, Dev at weitling wrote: The Cocoon directory structure isn't very concise: many directories with the same or at least similar names at different locations, some directories with non-intuitive names (e.g. lib/endorsed: why endorsed?). I can't agree. Cocoon 2.1, which you are probably using, has a quite simple directory structure. Not everything might be obvious on the first sight, but you might ask more specific questions to get it explained. The endorsed dir you refer to is nothing Cocoon specific, but a general Java 1.4 problem with XML libs: http://wiki.apache.org/cocoon/EndorsedLibsProblem. If there's a problem I don't know where to look, I don't know where to place my files, I don't know which parts are superfluous and and and... There is some documentation available to get started. Furthermore you can have a look into the block structure and adapt one, especially the tour block, which introduces the most important ones: http://cocoon.zones.apache.org/demos/release/samples/blocks/tour/intro/docs/index.html (also available in your local installation). Later one you should not integrate your code into Cocoon's build, but integrate Cocoon into your build. Jörg
Explanation of the Cocoon directory structure
Hi! The Cocoon directory structure isn't very concise: many directories with the same or at least similar names at different locations, some directories with non-intuitive names (e.g. lib/endorsed: why endorsed?). If there's a problem I don't know where to look, I don't know where to place my files, I don't know which parts are superfluous and and and... Are docs about that anywhere in the outside world without having to pay $ 30 for an outdated book? Bye, Florian
