Re: [announce] test documentation

2003-12-11 Thread bernhard huber
hi, Welcome home Bernhard, nice to see you back here. yup, i was a bit busy at work BTW, is there a way to just run individual tests, or does 'build test' need to just run them all. well, if you want to edit tool/targets/test-build.xml, adopting the target junit-tests, and

RE: cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/source/impl SitemapSource.java

2003-12-11 Thread Carsten Ziegeler
Giacomo Pati wrote: Carsten Ziegeler wrote: Vadim Gritsenko wrote: -this.reset(); -this.init(); +reset(); +init(); Why do you make these changes? A long time ago, we decided that this.method() is more readable and we want to use that :)

DO NOT REPLY [Bug 25433] New: - [PATCH] Sitemap Viewer

2003-12-11 Thread bugzilla
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=25433. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25433] - [PATCH] Sitemap Viewer

2003-12-11 Thread bugzilla
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=25433. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25433] - [PATCH] Sitemap Viewer

2003-12-11 Thread bugzilla
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=25433. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25433] - [PATCH] Sitemap Viewer

2003-12-11 Thread bugzilla
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=25433. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25437] New: - [PATCH] TreeProcessor.ForwardEnvironmentWrapper should delegate isResponseModified/setResponseIsNotModified to wrapped environment

2003-12-11 Thread bugzilla
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=25437. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25437] - [PATCH] TreeProcessor.ForwardEnvironmentWrapper should delegate isResponseModified/setResponseIsNotModified to wrapped environment

2003-12-11 Thread bugzilla
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=25437. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Fwd: Bug in session-fw logicsheet (?)

2003-12-11 Thread Stephanie Zohner
--- Weitergeleitete Nachricht / Forwarded Message --- Date: Wed, 10 Dec 2003 16:22:44 +0100 (MET) From: Stephanie Zohner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Bug in session-fw logicsheet (?) Hi, I came accross the following problem recently, and I would like to know if this is a bug

DO NOT REPLY [Bug 25437] - [PATCH] TreeProcessor.ForwardEnvironmentWrapper should delegate isResponseModified/setResponseIsNotModified to wrapped environment

2003-12-11 Thread bugzilla
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=25437. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Naming of -dev libraries

2003-12-11 Thread Sylvain Wallez
Hi all, I noticed that all development version of libraries are now named -dev.jar with no indication of the date as we had some time ago. Although it is certainly convenient for the updater since it avoids deleting/adding a jar and modifying jars.xml, it's absolutely not convenient for users

DO NOT REPLY [Bug 25445] New: - JXForms xf:hidden doesn't get value

2003-12-11 Thread bugzilla
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=25445. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25447] New: - Bug in Xalan 2.5.2

2003-12-11 Thread bugzilla
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=25447. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: Naming of -dev libraries

2003-12-11 Thread Vadim Gritsenko
Sylvain Wallez wrote: Hi all, I noticed that all development version of libraries are now named -dev.jar with no indication of the date as we had some time ago. Although it is certainly convenient for the updater since it avoids deleting/adding a jar and modifying jars.xml, it's absolutely

DO NOT REPLY [Bug 25422] - deadlock in ClearPersistentStoreAction

2003-12-11 Thread bugzilla
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=25422. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25429] - DELI incorrectly caching content

2003-12-11 Thread bugzilla
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=25429. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25422] - deadlock in ClearPersistentStoreAction

2003-12-11 Thread bugzilla
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=25422. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: [POLL] Interest in unified code convention

2003-12-11 Thread Ross Gardler
David Crossley wrote: As we discussed in the other Whitepace thread [1] there are many issues with this, so we need to tread carefully. Imagine that someone was doing major work on a certain component. When they do a 'cvs update' then they would get massive cvs conflicts. [1]

DO NOT REPLY [Bug 25437] - [PATCH] TreeProcessor.ForwardEnvironmentWrapper should delegate isResponseModified/setResponseIsNotModified to wrapped environment

2003-12-11 Thread bugzilla
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=25437. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25437] - [PATCH] TreeProcessor.ForwardEnvironmentWrapper should delegate isResponseModified/setResponseIsNotModified to wrapped environment

2003-12-11 Thread bugzilla
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=25437. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: cvs commit: cocoon-2.1/lib/core excalibur-component-20031126.jar excalibur-store-1.0-dev.jar

2003-12-11 Thread Christian Haul
[EMAIL PROTECTED] wrote: sylvain 2003/12/11 10:19:05 Modified:lib jars.xml Removed: lib/core excalibur-component-20031126.jar excalibur-store-1.0-dev.jar -libcore/excalibur-component-20031126.jar/lib +libcore/excalibur-component-20031211

Re: cvs commit: cocoon-2.1/lib/core excalibur-component-20031126.jar excalibur-store-1.0-dev.jar

2003-12-11 Thread Sylvain Wallez
/excalibur-component-20031211.jar/lib Sylvain, would you mind also adding the new jar ;-) ? Ooops, done :-/ That's what happens when you want to commit too quickly before leaving work to go home after a tiring day... Sorry, Sylvain -- Sylvain Wallez Anyware

Store fixed

2003-12-11 Thread Sylvain Wallez
Hi all, I fixed the store according to the recent discussion: - the transient-store is really transient, and its default implementation forbid to set user-persistent-store to true. - the store is a memory store backed by the persistent-store All stores are now instrumented and provide 3

New cocoon.setupObject() and cocoon.disposeObject()

2003-12-11 Thread Sylvain Wallez
Hi team, As per the discussion following the new cocoon.setupObject(obj) method, I added to new methods to the FOM: - cocoon.createObject(class) creates an object and goes through the various Avalon lifecycle interfaces. The class attribute can be either a Class (written

processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Sylvain Wallez
One more new feature ;-) Following the thread extending FOM about extending processPipelineTo to SAX and DOM, I wrote a utility class that handles all this. This class is totally decorrelated from the FOM and the cocoon object and provides the processToDOM(), processToSAX() and

Moved ParanoidCocoonServlet to its own block

2003-12-11 Thread Sylvain Wallez
Last one for today ;-) I moved the ParanoidCocoonServlet and associated classes to a new paranoid block? Why this? Because ParanoidCocoonServlet is actually a generic servlet wrapper that can shield _any_ servlet in a ParanoidClassLoader. Moving it to its own block leads to having a

RE: processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Unico Hommes
Sylvain Wallez wrote: One more new feature ;-) Following the thread extending FOM about extending processPipelineTo to SAX and DOM, I wrote a utility class that handles all this. This class is totally decorrelated from the FOM and the cocoon object and provides the

Re: processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Tony Collen
Sylvain Wallez wrote: One more new feature ;-) Following the thread extending FOM about extending processPipelineTo to SAX and DOM, I wrote a utility class that handles all this. This class is totally decorrelated from the FOM and the cocoon object and provides the processToDOM(),

Re: New cocoon.setupObject() and cocoon.disposeObject()

2003-12-11 Thread Tony Collen
Sylvain Wallez wrote: Hi team, As per the discussion following the new cocoon.setupObject(obj) method, I added to new methods to the FOM: - cocoon.createObject(class) creates an object and goes through the various Avalon lifecycle interfaces. The class attribute can be either a Class

Re: processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Sylvain Wallez
Tony Collen wrote: Sylvain Wallez wrote: One more new feature ;-) Following the thread extending FOM about extending processPipelineTo to SAX and DOM, I wrote a utility class that handles all this. This class is totally decorrelated from the FOM and the cocoon object and provides the

Re: Naming of -dev libraries

2003-12-11 Thread David Crossley
Vadim Gritsenko wrote: Sylvain Wallez wrote: snip/ Was there a discussion about this that I missed, and if not, what do you think of using -dev-mmdd.jar names? -1 to -dev, +1 to whatever-yyymmdd, whatever may include dev for those who want it. I agree entirely. In fact this has

Re: processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Sylvain Wallez
Unico Hommes wrote: Sylvain Wallez wrote: One more new feature ;-) Following the thread extending FOM about extending processPipelineTo to SAX and DOM, I wrote a utility class that handles all this. snip/ Damn dude, you just keep 'em coming ;-) Excellent! This is going to be s

Re: processPipelineTo[Stream|SAX|DOM]

2003-12-11 Thread Tony Collen
Sylvain Wallez wrote: Tony Collen wrote: Sylvain Wallez wrote: snip So what about deprecating cocoon.processPipelineTo from the official FOM and direct users to the new class ? I'm +0 on this. I'm not sure where someone would specifically want an OutputStream rather than a DOM document,

Re: Caching Questions

2003-12-11 Thread daltonj
Thanks for the explanation. I am a little bit disappointed by the number of test cases, but I guess that means there is a lot of work to be done! I will probably end up writing some for my project and contribute them. What is the upcoming caching work, if I may ask. - Jeff Quoting David

Re: Caching Questions

2003-12-11 Thread David Crossley
Please do not Cc messages to people. Sending to [EMAIL PROTECTED] will suffice. daltonj wrote: Thanks for the explanation. I am a little bit disappointed by the number of test cases, but I guess that means there is a lot of work to be done! That is correct. This is essentially a volunteer

DO NOT REPLY [Bug 25403] - [PATCH] EncodeURLTransformer unconditionally creates session

2003-12-11 Thread bugzilla
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=25403. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: Moved ParanoidCocoonServlet to its own block

2003-12-11 Thread Stefano Mazzocchi
On 11 Dec 2003, at 13:53, Sylvain Wallez wrote: Last one for today ;-) I moved the ParanoidCocoonServlet and associated classes to a new paranoid block? Why this? Because ParanoidCocoonServlet is actually a generic servlet wrapper that can shield _any_ servlet in a ParanoidClassLoader. Moving

Re: Naming of -dev libraries

2003-12-11 Thread Stefano Mazzocchi
On 11 Dec 2003, at 14:16, David Crossley wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: snip/ Was there a discussion about this that I missed, and if not, what do you think of using -dev-mmdd.jar names? -1 to -dev, +1 to whatever-yyymmdd, whatever may include dev for those who want it. I

DO NOT REPLY [Bug 25433] - [PATCH] Sitemap Viewer

2003-12-11 Thread bugzilla
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=25433. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25381] - consistent line-endings for all text files

2003-12-11 Thread bugzilla
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=25381. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.