Hi,
I think there is a typo in cocoon-sitemap-1.0.xsd (in
core/cocoon-sitemap/cocoon-sitemap-impl/src/main/resources/org/apache/co
coon/sitemap/schema). At line 334, 'xs:ID' should be changed to
'xsd:ID'. See the patch below.
Do I need to create a JIRA issue for this?
Thanks,
Bart.
Index:
Quoting Bart Molenkamp [EMAIL PROTECTED]:
Hi,
I think there is a typo in cocoon-sitemap-1.0.xsd (in
core/cocoon-sitemap/cocoon-sitemap-impl/src/main/resources/org/apache/co
coon/sitemap/schema). At line 334, 'xs:ID' should be changed to
'xsd:ID'. See the patch below.
Do I need to create a
The repository block contains a the CachingSource. Does anybody have experiences
with it?
I wonder how I can configure it so that the cached source expires e.g. after 5
minutes but if it can't be updated (e.g. the wrapped source isn't available),
the expired version should be used. I would
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 26 March 12:03 PM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2007-03-26 12:02:08
... Rendering docs in
Online report :
http://vmbuild.apache.org/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/291/buildId/90374
Build statistics:
State: Error
Previous State: Ok
Started at: Mon, 26 Mar 2007 05:03:06 -0700
Finished at: Mon, 26 Mar 2007 05:05:22 -0700
Total time: 2m
Hello Reinhard,
The repository block contains a the CachingSource. Does
anybody have experiences
with it?
Yes, we do have a lot of experience with it (though we have a slightly
different version (Max Pfingsthorn changed it: the public SourceValidity
getValidity() returns an
Ard Schrijvers wrote:
Hello Reinhard,
The repository block contains a the CachingSource. Does
anybody have experiences
with it?
Yes, we do have a lot of experience with it (though we have a slightly different version (Max Pfingsthorn changed it: the public SourceValidity getValidity()
yes, the broken connection scenario is that what I want. If
you say that it
doesn't really fit into the caching source, what do you
propose instead?
It does fit in the current caching source without touching the caching source I
think :-)
Writing
another source wrapping source
Reinhard Poetz wrote:
The repository block contains a the CachingSource. Does anybody have
experiences with it?
Yes.
I wonder how I can configure it so that the cached source expires e.g.
after 5 minutes but if it can't be updated (e.g. the wrapped source
isn't available), the expired
Oops, should have read it in full...
Reinhard Poetz wrote:
I can think of setting the expires parameter to -1 and using a
background-refresher but this seems to be overly complex for this simple task.
Yes async will do the trick. And IMHO it should be Ok to alter sync
implementation to keep
Vadim Gritsenko wrote:
Oops, should have read it in full...
Reinhard Poetz wrote:
I can think of setting the expires parameter to -1 and using a
background-refresher but this seems to be overly complex for this
simple task.
Yes async will do the trick. And IMHO it should be Ok to alter
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Oops, should have read it in full...
Reinhard Poetz wrote:
I can think of setting the expires parameter to -1 and using a
background-refresher but this seems to be overly complex for this
simple task.
Yes async will do the trick. And IMHO it
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Oops, should have read it in full...
Reinhard Poetz wrote:
I can think of setting the expires parameter to -1 and using a
background-refresher but this seems to be overly complex for this
simple task.
Yes async will do
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Oops, should have read it in full...
Reinhard Poetz wrote:
I can think of setting the expires parameter to -1 and using a
background-refresher but this seems to be overly complex for this
simple
Reinhard Poetz napisał(a):
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Actually it already should be working this way? See CachingSource line
427.
I guess with some additional configuration it should be possible to get
this stuff working but ...
TBH, I only want to have a url like
Daniel Fagerstrom napisał(a):
Grzegorz Kossakowski skrev:
The proposal looks good, so I propose that you submit it.
I just got home from a conference and have to get up early tomorrow so I
don't have the time to do a detailed review.
In you description of converters you maybe should mention
Online report :
http://vmbuild.apache.org/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/291/buildId/90731
Build statistics:
State: Ok
Previous State: Error
Started at: Mon, 26 Mar 2007 12:01:02 -0700
Finished at: Mon, 26 Mar 2007 12:01:12 -0700
Total time: 9s
[
https://issues.apache.org/jira/browse/COCOON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski reassigned COCOON-2028:
Assignee: Grzegorz Kossakowski
Typo in xsd
---
[
https://issues.apache.org/jira/browse/COCOON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2028.
Resolution: Fixed
Done. Fixed schema should be available within few hours.
Typo
19 matches
Mail list logo