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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

webdav block cleanup (Was: whitespace cleanup and efficiency drive)

If anyone is working in the webdav block, then would they please commit any outstanding stuff. Sometime mid next week i would like to fix all the dos2unix problems in there. If you want me to hold off for a while, then please say so. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25381 --David

Re: Naming of "-dev" libraries

On 11 Dec 2003, at 14:16, David Crossley wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: 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

Re: Moved ParanoidCocoonServlet to its own block

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. Movin

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Caching Questions

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 c

Re: Caching Questions

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 Cr

Re: processPipelineTo[Stream|SAX|DOM]

Sylvain Wallez wrote: Tony Collen wrote: Sylvain Wallez wrote: 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, but t

Re: processPipelineTo[Stream|SAX|DOM]

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. Damn dude, you just keep 'em coming ;-) Excellent! This is going to be s useful. N

Re: Naming of "-dev" libraries

Vadim Gritsenko wrote: > Sylvain Wallez wrote: > > > > 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 thi

Re: processPipelineTo[Stream|SAX|DOM]

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 pro

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

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 (writ

Re: processPipelineTo[Stream|SAX|DOM]

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(), processT

RE: processPipelineTo[Stream|SAX|DOM]

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 p

Moved ParanoidCocoonServlet to its own block

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 "cocoon-

processPipelineTo[Stream|SAX|DOM]

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 processToStr

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

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 Packages.my.packag

Store fixed

Hi all, I fixed the store according to the recent discussion: - the is really transient, and its default implementation forbid to set "user-persistent-store" to true. - the is a memory store backed by the All stores are now instrumented and provide 3 instruments : size, hits (successful look

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

-component-20031211.jar 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 Technologies

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

[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 -core/excalibur-component-20031126.jar +core/excalibur-component-20031211.jar Sylvain

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [POLL] Interest in unified code convention

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] http://marc.theaim

DO NOT REPLY [Bug 25422] - deadlock in ClearPersistentStoreAction

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 25422] - deadlock in ClearPersistentStoreAction

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Naming of "-dev" libraries

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 n

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Naming of "-dev" libraries

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 user

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Fwd: Bug in session-fw logicsheet (?)

--- 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 b

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

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

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

Re: [cforms] Binding jxpath like "name()"?

Sylvain Wallez wrote: Marc Portier wrote: I've never tried this, but sounds like a limitation of the jxpath() lib? what is exactly the effect of doing the path="name()" thing? You can use it for reading, but not for writing. JXPath only allows to set the value of nodes, which "name()" is no

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

Giacomo Pati wrote: Carsten Ziegeler wrote: Vadim Gritsenko wrote: -this.reset(); -this.init(); +reset(); +init(); It make sense for member variables but there I'd like to add a prefix like m_ which cannot be forgotten (as like the 'this.' prefix) and thus

Re: [announce] test & documentation

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 block-