Cocoon 2.1 will stay around for a while so same here!
Jeroen
Antonio Gallardo wrote:
Bertrand Delacretaz escribió:
Agree with Ralph, there's no need to close anything, if people want
to fix bugs on older versions that's one of the beauties of open
source: no one forces you to upgrade, as long
Hello,
Grzegorz Kossakowski wrote:
Could you elaborate on the known differences between CInclude
and Include transformers? Was it discussed somewhere?
I am not sure if it was ever discussed somewhere, but I can elaborate a
little on it ( though it has been a while, so I might be a little off
AFAIU, the
IncludeTransformer can only be cached by defining some
Above is ofcourse a typo...I was talking about the CIncludeTransformer
which can only be cached by some expires...
expires. Clearly, you cannot really know how to set this, or
if you fetch an external http source, just
Ard Schrijvers wrote:
snip/
Now, the IncludeTransformer adds the validity object of the included
sources to the validity object of the calling pipeline (pfff).
Let's have an example:
someXML.xml :
doc
include:include src=cocoon://fetchSnippet/
/doc
map:match pattern=main
Vadim Gritsenko wrote:
Indeed. I think this is a failure on CocoonSource part.
CocoonSource content depends on the sitemap.xmap, but
CocoonSource validity does not include validity of the
sitemap. As a result, even if sitemap is changed,
CocoonSource validity stays valid.
I'm not
Since I've been running successfully two of my custom Cocoon 2.2 apps with
Spring 2.5-rc2
(http://opensource.atlassian.com/projects/spring/browse/SPR-4081), I upgraded
trunk to use Spring 2.5. Since it is aimed to be a drop-in replacement for
2.0.x, I don't expect problems. Doing the upgrade
Issue Subscription
Filter: COCOON-open-with-patch (107 issues)
Subscriber: cocoon
Key Summary
COCOON-2137 XSD Schemas for CForms Development
https://issues.apache.org/jira/browse/COCOON-2137
COCOON-2133 Addition of allow-enlarge parameter to ImageOp resize operation
Reinhard Poetz skrev:
Since I've been running successfully two of my custom Cocoon 2.2 apps
with Spring 2.5-rc2
(http://opensource.atlassian.com/projects/spring/browse/SPR-4081), I
upgraded trunk to use Spring 2.5. Since it is aimed to be a drop-in
replacement for 2.0.x, I don't expect
Ard Schrijvers wrote:
Vadim Gritsenko wrote:
Indeed. I think this is a failure on CocoonSource part.
CocoonSource content depends on the sitemap.xmap, but
CocoonSource validity does not include validity of the
sitemap. As a result, even if sitemap is changed,
CocoonSource validity stays
Daniel Fagerstrom wrote:
Now we can also think about merging Daniel's work on OSGi
(whiteboard), which requires Spring-OSGi, with trunk. Daniel, maybe
you can share your thoughts on what this would mean for trunk (build
system, required code changes, etc.) and how we can keep the
experimental
10 matches
Mail list logo
