Ralph Goers wrote:
Mansour wrote:
It's working NOW. Can not thank you enough for this!
Now, let's figure out why it was failing. I was following the
tutorial on
http://cocoon.apache.org/2.1/howto/howto-html-pdf-publishing.html
and I obtained the site map contents from their. If the site map was
missing something, how did you know that this is caused by the
contents of the cocoon.xconf ??
This tells me that the sitemap is read before cocoon.xconf, and
contents of the later has to be initialized by the former ! Am I right ?
When you build Cocoon 2.1 by running build.sh using the defaults there
will be a sitemap.xmap in build/webapp. This sitemap is the root and
shouldn't be changed much (if you do you should know what you are
doing) as it contains all kinds of definitions you need. You would
then put your sitemap in a directory below this similar to the
sitemap.xmap in the samples directory. Your sitemap inherits the stuff
in the root sitemap. If I understand what you did correctly, the
problem was that you replaced the root sitemap with your own which
didn't contain any of the stuff you needed.
This is a very good piece of info. Now I understand that we have
"Global" sitemap.xconf and "local" one. So this tells me that when I
follow the tutorials and run my Cocoon application, I am basically
running it under the Global config, but overriding them with my own. So
I was not deploying directly to tomcat, but to Cocoon "platform" (and
not framework) which is running in tomcat? cool!
The cocoon build will also create cocoon.xconf and put the definitions
you need for the desired blocks in it. You should only modify it if
you are adding your own components. Again, you'll only do this if you
know what you are doing and have a reason.
That's what I am trying to do. I am trying to know what I am doing.
So, in short, with 2.1 the best way to build your own Cocoon
application is to follow the directions and edit
local.build.properties and local.blocks.properties to suit your needs.
Then go on from there.
As others have stated, the process with 2.2 is very different than
this and is hopefully easier. If you have problems trying to build 2.2
feel free to keep asking for help.
I did not have any difficulties with the build. It's maven !! how can it
fail. I was having difficulties understanding how the config files fit
together and the role and contents for each of them. :)
HTH
Ralph
---------------------------------------------------------------------
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]
