Sylvain,
Thanks a lot for your anwser.
I check the URIs through a servlet with the build-in jetty, and they
work fine, without generating any Exception. I dont think that the
problem comes from there, since the CLI does generate the URI I'am
asking properly (but with these exceptions). The problem probably
stems from another file that cocoon cannot read ... but I really can't
figure out which one (I checked the logger config file, the
cocoon.xconf, and other resources declared in my CLI xconf file ...
they seem to be properly declared and found).
Any hint ?
I've just spotted in your original message that you gave the output of your run. It seems that the problem is in the Deli block. Do you use Deli? If not, I'd suggest rebuilding Cocoon without it and see how that goes.
To do that: copy blocks.properties to local.blocks.properties and, in local.blocks.properties, remove the hash (#) before the exclude exclude.block.deli=true line. Then do:
build clean
and then
build
Let me know how that goes.
Regards, Upayavira
Upayavira,
I rebuild cocoon as you suggested. This indeed fixes my problem. I can now enjoy the full power of cocoon without misterious stack traces :-) Thanks a lot for your great help !
Warm regards,
Sylvain
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
