So the context protocol is pretty much useless in trunk. I replaced it
with blockcontext:/cocoon-core-main-sample/ and it works fine. It would
be a lot nicer to do blockcontext:// and get the current block context
but I'm not seeing anything keeping track of that.
Ralph
Ralph Goers wrote:
It
IIRC, context:// is supposed to refer to the current block context. The
servlet:context/@context-path attribute in the servlet service
configuration is used for setting up the curent block context.
In the cocoon-core-main-sample the curent block context is set up to be
On 4 Jan 2008, at 04:03, Joerg Heinicke wrote:
On 02.01.2008 11:26 Uhr, Robin Wyles wrote:
Looking at the pom I don't see any version numbers, but the
dependencies seem to be:
cocoon-core
cocoon-eventcache-impl
excalibur-datasource
servlet-api
From what I know in this case these versions
Hi,
I added[1] FAQ-entry for the subject of much controversy among Cocoon
community. Now I wonder how to
get it published, I found old document aggregating all FAQ entries but it
doesn't work ATM. Before I
go and fix it I would like to ask your opinion on separating FAQs for Cocoon
2.1 and
Grzegorz Kossakowski said the following on 5/1/08 13:51:
Hi,
I added[1] FAQ-entry for the subject of much controversy among Cocoon
community. Now I wonder how to
get it published, I found old document aggregating all FAQ entries but it
doesn't work ATM. Before I
go and fix it I would like to
Hello,
I was working on fixing documentation publishing and I quite satisfied with
results. At least most
of the documentation is being updated again. However, I noticed that
documentation for unreleased
blocks (like cocoon-profiler) is being published. Is it supposed to be that way?
--
On Jan 5, 2008, at 9:53 AM, hepabolu wrote:
Grzegorz Kossakowski said the following on 5/1/08 13:51:
Hi,
I added[1] FAQ-entry for the subject of much controversy among
Cocoon community. Now I wonder how to
get it published, I found old document aggregating all FAQ entries
but it doesn't
