Hi,
I noticed the following on this page
(http://cocoon.zones.apache.org/daisy/cdocs-core/g2/g1/g2/688.html):
As usual, we will make the results cacheable because that is just good
policy. In the spirit of trying to be useful, as well as trying to keep
things manageably simple, let's create
Hi,
I am trying to work out the best approach for developing for Cocoon.
I have downloaded the full source and I have run mvn -P allblocks
eclipse:eclipse on the base pom. I also ran mvn -Dmaven.test.skip=true
-Pallblocks install. I guess my next question is where to from here? I
have also
Kamal wrote:
Hi,
I am trying to work out the best approach for developing for Cocoon.
I have downloaded the full source and I have run mvn -P allblocks
eclipse:eclipse on the base pom. I also ran mvn -Dmaven.test.skip=true
-Pallblocks install. I guess my next question is where to from here? I
I am not really a committer to Cocoon, but I was wondering about this
whole JXtemplates + Flowscript replaces XSPs advice. I feel that
JXTemplates + Flowscript is a poor substitute. Here are my reasons why:
1. It leads to an explosion in pipelines. Instead of one pipeline, you
now have 2 (at
[
https://issues.apache.org/jira/browse/COCOON-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604015#action_12604015
]
Ellis Pritchard commented on COCOON-2152:
-
IMHO this needs a complete re-factor
This is a thread that for time to time is being discussed. See:
http://markmail.org/message/uzilvg4ww35nmegk
Quoting from my mail in the thread:
As an old XSP user I think XSP is good for some rapid prototyping and
for some small sites (Matthew and Carsten book stated about it clearly).
The
