I am writing a tutorial about this. I am editing few mistakes and
testing the contents by following every step.
I will post the link as soon as I get it ready.
Joerg Heinicke wrote:
On 19.11.2007 16:33 Uhr, Reinhard Poetz wrote:
In Cocoon 2.2 the generate block contains a folder called COB-INF
which I think stands for Cocoon Block, may be. However, what is
this directory and where can I configure it's name?
Why would the root of the block be /COB-INF when referring to it in
the sitemap <map:generate src="demo/welcome.xml"/>
Then in the /META-INF/cocoon/spring/demo-application-context.xml
file it becomes <bean id="demo" class="demo.MyBean"
scope="singleton"> ?!!
I really don't understand this. I find it very confusing. Can
someone help here?
I found what I was looking for here
http://cocoon.apache.org/2.2/core-modules/core/2.2/1263_1_1.html
I 'll appreciate some comments about why is this structure for a block.
A Cocoon block may contain Java classes, component declerations
(Avalon and Spring style) and Cocoon applications. The directory
structure was derived from these needs because we had to make sure
that everything has its own place:
/COB-INF/** The Cocoon application (sitemaps, templates, etc.)
/META-INF/cocoon/** All configuration files
/** Java classes and Java resources
And yes, COB-INF stands for COcoon block and the name was chosen in
analogy to e.g. WEB-INF.
In the other thread you wrote [1]:
"Basically, you are trying to get the user to create a "block that
uses Cocoon" and deploy it to a Cocoon deployment. So in other word
you are making Cocoon a platform. The block that I created is not a
Cocoon application but an application that runs under Cocoon's
deployment."
This pretty much hits the nail on the head. A Cocoon block is to
Cocoon what a servlet is to a servlet container (or web app to web app
container). So you also find pretty much the same directory structure
in a Cocoon block and COB-INF matches WEB-INF as Reinhard wrote.
Joerg
[1] http://marc.info/?l=xml-cocoon-users&m=119548172028617&w=4
---------------------------------------------------------------------
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]
