cziegeler02/04/25 23:43:22
Modified:src/java/org/apache/cocoon/components
ExtendedComponentSelector.java
Log:
Fixing hasComponent() bug
Revision ChangesPath
1.2 +10 -1
ovidiu 02/04/26 00:01:08
Modified:src/scratchpad/schecoon/webapp/docs index.xml
Log:
Updated.
Revision ChangesPath
1.4 +9 -7 xml-cocoon2/src/scratchpad/schecoon/webapp/docs/index.xml
Index: index.xml
cziegeler02/04/26 00:19:13
Modified:src/java/org/apache/cocoon/sitemap
DefaultSitemapComponentSelector.java
Log:
Fixing hasComponent() bug
Revision ChangesPath
1.4 +9 -1
This is reposted to dev list because there was no answer on the users
list.
-Forwarded Message-
From: Nick Airey [EMAIL PROTECTED]
To: Cocoon Users [EMAIL PROTECTED]
Subject: Programmatic invalidation of cache
Date: 25 Apr 2002 17:29:55 +0100
Hello everyone,
I have some custom
If you know the key of the cached response, you could remove it
from the cache:
You can lookup the Store containing the cached responses - the
role for this is Store.TRANSIENT_CACHE - and then remove it by
hand.
Carsten
-Original Message-
From: Nick Airey [mailto:[EMAIL PROTECTED]]
cziegeler02/04/26 01:41:52
Modified:.changes.xml
src/java/org/apache/cocoon/components
CocoonComponentManager.java
src/java/org/apache/cocoon/environment
AbstractEnvironment.java SourceResolver.java
On April 26, 2002, Bertrand Delacretaz wrote:
Very helpful comments, Bert.
1) Tracks:
it might be worthwile at some point to create tracks into the
documentation, task-oriented reading guides.
For example: if you want to publish static XML to HTML, here's your
reading
list: FAQ 232,
Hi,
I have following problem:
Usually we have xsp like this:
xsp:page
page
...
esql:execute-query
...
/esql:execute-query
...
/page
/xsp:page
Because I have to repeat often the execute-query (with different arg) my idea was to
write:
xsp:page
xsp:logic
void myMethod(MyObject myArg) {
On Friday 26 April 2002 11:19, Diana Shannon wrote:
. . .
Do you think these need separate classification, or should they be
how-tos (with links to other how-tos), categorized as tracks?
. . .
I see the tracks as part of the navigation, which could be:
a) search-based (googling through the
I have been updating the sitemap DTD, using the
src\webapp\resources\entities\sitemap-v02.dtd file, and found that a lot of
attributes and elements are missing. ex. the logger attribute is not present.
I did it to use this DTD in XMLSpy to see all the possible attributes and
child elements of
cziegeler02/04/26 03:42:17
Modified:src/java/org/apache/cocoon Cocoon.java
src/java/org/apache/cocoon/components/language/markup
NamedLogicsheet.java
src/java/org/apache/cocoon/components/source
cziegeler02/04/26 04:01:33
Modified:src/java/org/apache/cocoon/components/url
ContextURLFactory.java ResourceURLFactory.java
URLFactory.java URLFactoryImpl.java
Log:
Deprecating more
Revision ChangesPath
1.5 +3 -1
Sylvain,
seems that I've found some strange/funny things. Looks like a bug somewhere
in the error handler. So, what happens:
* First scenario (i18n sitemap is misconfigured):
1. I request the URL: 'cocoon/samples/i18n/' - this should invoke its own
sitemap
2. sitemap fails with an exception
Bert Van Kets wrote:
I have been updating the sitemap DTD, using the
src\webapp\resources\entities\sitemap-v02.dtd file, and found that a lot of
attributes and elements are missing. ex. the logger attribute is not present.
Beware. Note the comments in the top of the DTD, wherein
it says
Hi,
I´m faced with a strange problem on using the xmldb protocol.
It is working perfektly when I use it in the sitemap as a source for the FileGenerator.
But it is not working in an stylesheet to pull a document out of a xmldb (Xindice)
Database.
Stylesheet:
xsl:stylesheet ...
...
Bröckelmann, Mathias wrote:
xsl:stylesheet ...
...
xsl:template match=foo
...
xsl:copy-of select=document('xmldb:xindice:///db/test/news/documentkey')/
...
/xsl:template
...
/xsl:stylesheet
Just a note: IIRC, using document() in an XSL stylesheet probably will
result in
Ivelin Ivanov wrote:
This should be referenced on the Cocoon Links page along with Ugo's
sample.
http://xml.apache.org/cocoon/cocoon-links.html
Yes, as a start. Or, perhaps someone -- Ugo, Pankaj? -- might consider
refactoring/donating it into official Cocoon documentation -- as a
how-to
Diana Shannon wrote:
Bertrand Delacretaz wrote:
1) Tracks:
it might be worthwile at some point to create tracks into the
documentation, task-oriented reading guides.
For example: if you want to publish static XML to HTML, here's your
reading
list: FAQ 232, FAQ 321, html
cziegeler02/04/26 04:54:11
Added: src/java/org/apache/cocoon/components/source SourceUtil.java
Log:
Adding util class
Revision ChangesPath
1.1
xml-cocoon2/src/java/org/apache/cocoon/components/source/SourceUtil.java
Index: SourceUtil.java
At 21:02 26/04/2002 +1000, you wrote:
Bert Van Kets wrote:
I have been updating the sitemap DTD, using the
src\webapp\resources\entities\sitemap-v02.dtd file, and found that a
lot of
attributes and elements are missing. ex. the logger attribute is not
present.
Beware. Note the
cziegeler02/04/26 05:21:53
Added: src/java/org/apache/cocoon/sitemap Sitemap.java
Log:
Accidentally removed
Revision ChangesPath
1.6 +0 -0 xml-cocoon2/src/java/org/apache/cocoon/sitemap/Sitemap.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8555.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8555.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi!
Just a hint: take a look at
xml-cocoon2\src\java\org\apache\cocoon\components\treeprocessor\treeprocesso
r-builtins.xml
, this file contains all the possible nodes with some restrictions on child
elements.
Btw, there was also an effort in developing a sitemap W3C Schema, but it
also died
cziegeler02/04/26 05:30:52
Modified:src/java/org/apache/cocoon/components/treeprocessor
TreeProcessor.java
src/webapp/WEB-INF cocoon.xconf
Log:
Adding file attribute to configure the place of the sitemap in the cocoon.xconf again
Revision
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8556.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8556.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
cziegeler02/04/26 05:33:38
Modified:src/java/org/apache/cocoon/components/treeprocessor
TreeProcessor.java
Log:
Adding check-reload behaviour to treeprocessor
Revision ChangesPath
1.8 +3 -3
cziegeler02/04/26 05:35:40
Modified:src/webapp/WEB-INF cocoon.xconf
Log:
Adding check-reload behaviour to treeprocessor
Revision ChangesPath
1.13 +9 -1 xml-cocoon2/src/webapp/WEB-INF/cocoon.xconf
Index: cocoon.xconf
Hi,
currently the TreeBuilderSelector is not a real Avalon Component,
it is configured in an XML file called treeprocessor-builtins.xml.
Can we make a real avalon component out of this and move the
configuration into the cocoon.xconf?
I think this would reduce the code of the treeprocessor in
Ovidiu,
Is there a way to generate an URI with the current continuation to the
sitemap?
Let´s say that I have defined a simplistic sitemap like this:
map:pipeline
map:match pattern=start
map:call function=startFunction/
/map:match
map:match pattern=doAction/*
map:act
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8557.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
-Ursprüngliche Nachricht-
Von: Michael Hartle [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 26. April 2002 13:22
An: [EMAIL PROTECTED]
Betreff: Re: xmldb protocol in xsl stylesheets is not working
Bröckelmann, Mathias wrote:
xsl:stylesheet ...
...
xsl:template
nicolaken02/04/26 07:09:22
Modified:src/documentation/xdocs/userdocs index.xml
src/documentation/xdocs/userdocs/serializers
xls-serializer.xml
src/java/org/apache/cocoon/components/elementprocessor/impl/poi/hssf
In AbstractSAXSource.java :
public AbstractSAXSource(Environment environment,
ComponentManager manager,
Logger logger) {
this.log = logger;
this.manager = manager;
}
Is there a reason to have environnement as a parameter ?
Depending on the samples, there are to different way of resolving the source
URL :
1- The Factory send the whole location to the Source's constructor, wich
deal with it
2- The Factory parse the location, and call the constructor with typed
parameters (or trhows MalformerURLException)
Is there
I just found two strange things about logging in Cocoon:
a) If the logger category for a component is not configured in the
cocoon.xconf
(via the logger attribute), it logs by default into core.manager.
According to the configuration in web.xml, this should be just core.
b) The following
TREGAN Fabien wrote:
Depending on the samples, there are to different way of resolving
the source
URL :
1- The Factory send the whole location to the Source's constructor, wich
deal with it
2- The Factory parse the location, and call the constructor with typed
parameters (or trhows
TREGAN Fabien wrote:
In AbstractSAXSource.java :
public AbstractSAXSource(Environment environment,
ComponentManager manager,
Logger logger) {
this.log = logger;
this.manager = manager;
}
Is there a reason to have
Gianugo Rabellino wrote:
TREGAN Fabien wrote:
In AbstractSAXSource.java :
public AbstractSAXSource(Environment environment,
ComponentManager manager,
Logger logger) {
this.log = logger;
this.manager = manager;
Carsten Ziegeler wrote:
Gianugo Rabellino wrote:
Definitely not. It was an oversight: the problem is that fixing it might
break some components. I'll take a look at it.
And you could rewrite them as avalon excalibur source objects... :)
Can you give some pointer on what the
Carsten Ziegeler wrote:
Michael Hartle wrote:
Can you give some pointer on what the differences between classical
Sources and Avalon Excalibur Source objects are ?
Ok, first of course the package name :)
snip-overview/
Thanks !
Best regards,
Michael Hartle,
Hartle Klug GbR
I just wanted to add, that I will try to keep updated information
on my newly created weblog (http://radio.weblogs.com/0107211/).
(ok, I'm only trying to top Matthews hit rate... :) )
Carsten
Open Source GroupsunShine - b:Integrated
kpiroumian02/04/26 09:17:38
Modified:src/webapp/samples/i18n menu2html.xsl simple.xsl simple.xsp
site2html.xsl sitemap.xmap
src/webapp/samples sitemap.xmap
Log:
Minor additions and corrections to i18n samples.
Revision ChangesPath
kpiroumian02/04/26 09:26:21
Modified:.changes.xml
Log:
Updates to i18n transformer and samples.
Revision ChangesPath
1.149 +8 -1 xml-cocoon2/changes.xml
Index: changes.xml
===
RCS
Hi all,
let me start with a short introduction of my company and what we have done so
far.
Before being founded on April 1, 2001 as BASF IT Services we were an integrated
part of BASF Aktiengesellschaft in Ludwigshafen, Germany and BASF Computer
Services in Europe. We focus on high-quality
Lewis, Andrew J wrote:
Many of you have probably seen my occassional comments on here - I
am mostly a lurker. But I wanted to let all of you know about the project I
am using Cocoon for (since December) - which only a couple of people on the
list knew about. I now have permission to
Carsten Ziegeler wrote:
Hi,
currently the TreeBuilderSelector is not a real Avalon Component,
it is configured in an XML file called treeprocessor-builtins.xml.
picky-mode
What makes it not a real Avalon component that its class name is
hardcoded in TreeProcessor, not that its configuration
On Friday 26 April 2002 10:46 am, Carsten Ziegeler wrote:
b) The following lines in the cocoon.xconf make me a little bit wonder:
category name=core log-level=DEBUG
category name=startup log-level=DEBUG/
category name=roles log-level=DEBUG/
category name=manager
sylvain 02/04/26 13:26:54
Modified:
src/scratchpad/schecoon/src/org/apache/cocoon/components/treeprocessor/sitemap
ContinueNode.java CallFunctionNode.java
Log:
Some help to cut dependencies of Interpreter on TreeProcessor
Revision ChangesPath
1.5
-Original Message-
From: Diana Shannon
Ivelin Ivanov wrote:
This should be referenced on the Cocoon Links page along with Ugo's
sample.
http://xml.apache.org/cocoon/cocoon-links.html
Yes, as a start.
I have created a separate Cocoon Resources page to aggregate all my Cocoon
On Fri, 26 Apr 2002 15:02:55 +0200, =?iso-8859-1?Q?Mats_Nor=E9n?= [EMAIL PROTECTED] wrote:
Ovidiu,
Is there a way to generate an URI with the current continuation to the
sitemap?
Let´s say that I have defined a simplistic sitemap like this:
map:pipeline
map:match pattern=start
Impressive !
Isn't this a generalized implementation of Berin's call back proposal.
I like it. It steals away the most powerful concept from JSPs and gives it
to Cocoon.
How did you guys do input/form handling?
Ivelin
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL
53 matches
Mail list logo
