RE: Encoding problems

Santiago Gala wrote: > Re: cache comments later: > > When I was discussing Cocoon (then new) cache ideas with Ricardo > Rocha, (so around winter 2000/spring 2001) I sent an idea to Cocoon-dev > about propagating the CacheValidity to set the Expires in the seriazed > output. It looked like a

Re: does xpointer still work?

On Tue, Mar 11, 2003 at 11:58:22PM +0100, Michael Wechner wrote: > Hi > > it seems to me that xpointer doesn't work anymore. Does > anyone else have the same experience? > > This works: > > > > and this does not work anymore: > > I remember encountering same thing. IIRC the workaround is t

RE: cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/xscript XScriptObject.java XScriptObjectFromURL.java XScriptObjectInlineXML.java

Stefano Mazzocchi wrote: > BTW, what's the status of the 'deprecation' transition? what's left to > do? are we able to compile the core without the deprecated classes yet? > > Anyway, thanks to both you and Carsten for helping out on this. It would > have been a nightmare to do it alone. > I p

EnvironmentWrapper.java

Hi Carsten, Lengthy rational below; maybe just skip to the attachments. Related to old bug 10281. It's popped up again just as your commit comments said it would. Thanks (and to Ugo) for fixing the ForwardRedirector problems too. This is completely unrelated to the ForwardRedirector Problem/Fi

Re: [RT] Cocoon's own publishing system

Steven Noels wrote: Sam Ruby wrote: I have some scripts that do all that and more. But you already knew that. ;-) OK, I'm giving in. Given some time and energy, Cocoon, docs included, will be built regularily on cocoondev.org, along with some other projects, by means of some tool written by so

Re: DOMStreamer DOM 1 support?

Jeff Turner wrote: On Tue, Mar 11, 2003 at 12:39:18PM +0100, Bruno Dumon wrote: On Tue, 2003-03-11 at 09:15, Jeff Turner wrote: On Tue, Mar 11, 2003 at 08:14:21AM +0100, Bruno Dumon wrote: On Tue, 2003-03-11 at 07:37, Jeff Turner wrote: Probably a question for Bruno.. The

Re: Encoding problems

Stefano Mazzocchi wrote: Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set pro

does xpointer still work?

Hi it seems to me that xpointer doesn't work anymore. Does anyone else have the same experience? This works: and this does not work anymore: Thanks Michael

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

Steven Noels wrote: So when Lenya ever exits from the (DOA) incubator, where should it be ^ Sorry about these nasty remarks - I should remember to live up to my own mail guidelines posted only hours ago. Duh. My bad. -- Steven Noels

Re: [RT] Cocoon's own publishing system

Sam Ruby wrote: I have some scripts that do all that and more. But you already knew that. ;-) OK, I'm giving in. Given some time and energy, Cocoon, docs included, will be built regularily on cocoondev.org, along with some other projects, by means of some tool written by some bearded script gu

Re: build system - status of filtering

Stefano Mazzocchi wrote, On 11/03/2003 19.53: Christian Haul wrote: ... Strangely enough, a quick look at blocks-build.xsl seems to indicate that files in the conf directory are filtered. Hints anybody? Yes. the indications are now located in a build.xml file located inside the block. Unfortunat

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

Steven Noels wrote: Stefano Mazzocchi wrote: Since we are a top level project, we are going to provide (url-) space for subprojects. Hmmm, that would be against the indications of the ASF that wants each PMC to control one and only one codebase, just like HTTPD has always done and works very

Re: [RT] Cocoon's own publishing system

Steven Noels wrote: I'm happy to trigger scripts or check on their regular operations once they are installed, but am a bit swamped ATM to come up with some scripts myself. So anyone who wants to give it a whirl just tell me and I'll be at your service. Cronifying "build docs" with some nagging

Re: [RT] Cocoon's own publishing system

On Tue, 11 Mar 2003, Diana Shannon wrote: > I agree 100% with Andrew that two "clearly" separated repositories won't > really improve on what we had. But it's all we have at the moment. Sure. I'm happy to help try and refactor it down to one archive. Or perhaps we could set up cocoon-docs with th

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

Stefano Mazzocchi wrote: Since we are a top level project, we are going to provide (url-) space for subprojects. Hmmm, that would be against the indications of the ASF that wants each PMC to control one and only one codebase, just like HTTPD has always done and works very well. So, we should

Re: [RT] Cocoon's own publishing system

Stefano Mazzocchi wrote: 1) repository is CVS on icarus. as it is today. no changes required in the editing/authoring process (for now, at least) 2) automated staging server is moof (or nagoya) I'd suggest to install it on moof (or nagoya) [moof is a macosx server donated to the ASF by apple a

Re: [RT] Cocoon's own publishing system

On Tuesday, March 11, 2003, at 10:49 AM, Stefano Mazzocchi wrote: 1. Many, many committers weren't updating release and head branches with their doc updates. It took time to scrutinize differences in the branches, to make sure all relevant docs were in the release branch, which is what is used

Re: [GUMP] Build Failure - Cocoon

[EMAIL PROTECTED] wrote: cocoon-block-fop: cocoon-block-fop-compile: fop-build: fop-mocks: fop-prepare: [mkdir] Created dir: /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030311/blocks/fop/dest [copy] Copying 1 file to /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030311/blocks/fop

Re: build system - status of filtering

> the ideal solution would be to give its block the ability to define its > own build customizations, but ant doesn't have this 'inheritance' concept :/ > > So i don't really know what to do. > > Suggestions? Please see the "esql samples" thread If noone objects I'll remove the filtering (an

Re: [RF] Entropy Killed the Cat

Stefano Mazzocchi wrote: The discussion is about making the flow a technology that cocoon can depend on for years. And this passes thru stabilizing the contracts between the flow scripters and the cocoon internals. And I want this to be done by a community, not by only the few developers that

Re: Snapshot links at Cocoon website

Diana Shannon wrote: 2. Updating the live site repository is time consuming, at least for me, on a slow dial-up connection (I live in a rural area of the US with no broadband option). The api docs directory is the time killer here. I spent eight hours, one night, simply performing a cvs update

Re: build system - status of filtering

Stefano Mazzocchi wrote: Christian Haul wrote: Team, after looking at the current samples it appears that src/blocks/databases/conf/datasources.xconf not filtered during the build. Thus the datasource to connect to for the datbase samples is invalid. ahhh, you're right, I forgot about thati

Re: Eclipse javac is screwed?

It just indicates whether the compiler should accept java 1.4 source extensions like "assert". It's equivalent to: javac -source 1.4 ... Vadim Gritsenko wrote: Christopher Oliver wrote: OK. But, I think you should also set the source version. What do you think? I was (and still am) not sure

Re: Rhino with continuations cvs

Stefano Mazzocchi wrote: BTW, do you have any news on the merging your patches into the main rhino tree at mozilla.org? Honestly, I don't think that will happen any time soon. My changes were based on a snapshot from March of last year. During that time one of the Rhino developers has modifie

Re: cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/xscriptXScriptObject.java XScriptObjectFromURL.java XScriptObjectInlineXML.java

Vadim Gritsenko wrote: Carsten Ziegeler wrote: Great Vadim! Many thanks! This was a bit too early... But now I think I have finished, and xscript/soap samples are still working. PS Thanks to Stefano - new welcome screen looks nice. Now we need only to fix tons of regression bugs, and then c

Re: build system - status of filtering

Christian Haul wrote: Team, after looking at the current samples it appears that src/blocks/databases/conf/datasources.xconf not filtered during the build. Thus the datasource to connect to for the datbase samples is invalid. ahhh, you're right, I forgot about thatit's the only thing that I c

Re: Rhino with continuations cvs

Christopher Oliver wrote: Stefano Mazzocchi wrote: Christopher Oliver wrote: Just wanted to let people know that thanks to Steven Noels and Ovidiu the Rhino interpreter with continuations recently got a CVS repository at cocoondev.org: http://cvs.cocoondev.org/cgi-bin/viewcvs.cgi/rhino1_5R4pre

Re: [ot] switcha

On Tue, 11 Mar 2003, Stefano Mazzocchi wrote: > Nils Mueller wrote: > >> that's not for linux :) > > > > > > you're runnnig OS-X though, aren't you? > > Oh, yes, I am. But I think Stephan is not. No, I'm not ;-) I prefer linux, it's for real men (I'm just joking ;-)). Stephan.

Re: Encoding problems

Amir Rosen wrote: -Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 8:22 PM To: [EMAIL PROTECTED] Subject: Re: Encoding problems Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the

Re: Eclipse javac is screwed?

Christopher Oliver wrote: OK. But, I think you should also set the source version. What do you think? I was (and still am) not sure what this flag mean that's why I left it off :) Vadim

RE: Encoding problems

> -Original Message- > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 8:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Encoding problems > > > Vadim Gritsenko wrote: > > Stefano Mazzocchi wrote: > > ... > > > >> On the other hand, by placing > >> > >>

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

Christian Haul wrote: On 12.Mar.2003 -- 12:54 AM, Jeff Turner wrote: (changing the topic so people notice its a vote) If I understand correctly, the proposed URL structure is: http://cocoon.apache.org/v1.x/ http://cocoon.apache.org/v2.0/ http://cocoon.apache.org/v2.1/ http://cocoon.apache.org/ -

Re: [ot] switcha

Nils Mueller wrote: that's not for linux :) you're runnnig OS-X though, aren't you? Oh, yes, I am. But I think Stephan is not. S.

Re: Encoding problems

Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set proper content-type header? D'o

Re: esql samples

Geoff Howard wrote: For now, though for purposes of reviving the samples quickly it may be as easy as re-commiting a new db.script into the database block with the changes in it. IIUC hsql uses this file as its persistent store of data - when you shut down, it gets overwritten with what is in

Re: esql samples

For now, though for purposes of reviving the samples quickly it may be as easy as re-commiting a new db.script into the database block with the changes in it. IIUC hsql uses this file as its persistent store of data - when you shut down, it gets overwritten with what is in memory. So, if you

Re: esql samples

Hm... I see. So it's enough to just copy the sql script into the WEB-INF/db location. I'll take look... I was just getting ready to see if there is an ant call to process a sql script over jdbc (I'm sure there is, just don't know ant well enough) but I'd make slow progress now as I'm very time li

Re: esql samples

At 12:33 PM 3/11/2003, you wrote: I wanted to look after the esql samples but found 1) the hsqldb not being filled (where did we do this before?) I noticed this a few days ago, but haven't had time to write about it. I'm pretty sure from experiencing adding a new table to the demo a month ago tha

Re: build system - status of filtering

Team, after looking at the current samples it appears that src/blocks/databases/conf/datasources.xconf not filtered during the build. Thus the datasource to connect to for the datbase samples is invalid. Well, did you miss the "esql samples" thread? ;) Strangely enough, a quick look at blocks-bui

Re: esql samples

I wanted to look after the esql samples but found 1) the hsqldb not being filled (where did we do this before?) I noticed this a few days ago, but haven't had time to write about it. I'm pretty sure from experiencing adding a new table to the demo a month ago that the hsqldb was not built aut

Re: Eclipse javac is screwed?

Vadim Gritsenko wrote: Christopher Oliver wrote: Hi Vadim, The EclipseJavaCompiler is currently hardcoded with source=1.4 and target=1.4. This is because I didn't know how to configure those properties through the available Cocoon interfaces. There is nothing wrong with the Eclipse compiler it

build system - status of filtering

Team, after looking at the current samples it appears that src/blocks/databases/conf/datasources.xconf not filtered during the build. Thus the datasource to connect to for the datbase samples is invalid. Strangely enough, a quick look at blocks-build.xsl seems to indicate that files in the conf d

Re: Rhino with continuations cvs

Stefano Mazzocchi wrote: Christopher Oliver wrote: Just wanted to let people know that thanks to Steven Noels and Ovidiu the Rhino interpreter with continuations recently got a CVS repository at cocoondev.org: http://cvs.cocoondev.org/cgi-bin/viewcvs.cgi/rhino1_5R4pre That's very good. BTW,

Re: Eclipse javac is screwed?

Christopher Oliver wrote: Hi Vadim, The EclipseJavaCompiler is currently hardcoded with source=1.4 and target=1.4. This is because I didn't know how to configure those properties through the available Cocoon interfaces. There is nothing wrong with the Eclipse compiler itself, only with my code

Re: Eclipse javac is screwed?

Hi Vadim, The EclipseJavaCompiler is currently hardcoded with source=1.4 and target=1.4. This is because I didn't know how to configure those properties through the available Cocoon interfaces. There is nothing wrong with the Eclipse compiler itself, only with my code. Either we can hardcode i

Re: [RT] Cocoon's own publishing system

"Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > So, here is the plan I propose: > > 1) repository is CVS on icarus. as it is today. no changes required in > the editing/authoring process (for now, at least) > > 2) automated staging server is moof (or nagoya) > > I'd suggest to install it on mo

Re: [RT] Cocoon's own publishing system

On Tue, 11 Mar 2003, Stefano Mazzocchi wrote: > Diana Shannon wrote: > > > 1. Many, many committers weren't updating release and head branches with > > their doc updates. It took time to scrutinize differences in the > > branches, to make sure all relevant docs were in the release branch, > > whic

Re: esql samples

At 11:15 AM 3/11/2003, you wrote: I wanted to look after the esql samples but found 1) the hsqldb not being filled (where did we do this before?) I noticed this a few days ago, but haven't had time to write about it. I'm pretty sure from experiencing adding a new table to the demo a month ago t

[GUMP] Build Failure - Cocoon

[echo] prepare: [echo] +---+ [echo] Apache Cocoon 20030311 [1999-2003]

esql samples

I wanted to look after the esql samples but found 1) the hsqldb not being filled (where did we do this before?) 2) the jdbc url, user and password not being replaced Did I miss something with the new build system? Can anyone provide me a pointer so I can fix it? Thanks -- Torsten smime.p7s Descr

[RT] Cocoon's own publishing system

Diana Shannon wrote: On Tuesday, March 11, 2003, at 05:32 AM, Pier Fumagalli wrote: I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Yes, but at that point we'll have to re-build the site once again... Ok, we shouldn't be so limited i

Re: Eclipse compiler targetting JDK 1.4

Marcus Crafter wrote: Hi Troops, Hope all is well. Some people on the users list discovered that the Eclipse Java compiler we're using for XSP is set to target a 1.4 runtime environment, which causes problems when running your application under 1.3. Any thoughts ? should we make the

Re: cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/xscriptXScriptObject.java XScriptObjectFromURL.java XScriptObjectInlineXML.java

Carsten Ziegeler wrote: Great Vadim! Many thanks! This was a bit too early... But now I think I have finished, and xscript/soap samples are still working. PS Thanks to Stefano - new welcome screen looks nice. Now we need only to fix tons of regression bugs, and then consider 2.1 well done.

Eclipse compiler targetting JDK 1.4

Hi Troops, Hope all is well. Some people on the users list discovered that the Eclipse Java compiler we're using for XSP is set to target a 1.4 runtime environment, which causes problems when running your application under 1.3. An

RE: cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/xscript XScriptObject.java XScriptObjectFromURL.java XScriptObjectInlineXML.java

Great Vadim! Many thanks! Carsten > Log: > Move from deprecated Cocoon source interface to Excalibur > source interface >

[VOTE] cocoon.apache.org URLs (Re: are we ready to move tococoon.apache.org?)

Perhaps http://cocoon.apache.org should contain *links* to the other urls mentioned below (instead of just redirecting to one of them), so visitors do not have to guess urls to find the documentation for various versions. Tim [EMAIL PROTECTED] 03/11/03 08:54AM >>> >(changing the topic so peo

Eclipse javac is screwed?

Got this: 09:36:38.789 WARN!! Error for /samples/xscript/simple java.lang.UnsupportedClassVersionError: org/apache/cocoon/www/samples/docs/samples/xscript/simple_xsp (Unsupported major.minor version 48.0) at java.lang.ClassLoader.defineClass0(Native Method) Seems like eclipse compiler is

Re: Snapshot links at Cocoon website

"Andrew Savory" <[EMAIL PROTECTED]> wrote: > On Tue, 11 Mar 2003, Diana Shannon wrote: > >> 1. Many, many committers weren't updating release and head branches with >> their doc updates. It took time to scrutinize differences in the >> branches, to make sure all relevant docs were in the release

Re: Snapshot links at Cocoon website

On Tue, 11 Mar 2003, Diana Shannon wrote: > 1. Many, many committers weren't updating release and head branches with > their doc updates. It took time to scrutinize differences in the > branches, to make sure all relevant docs were in the release branch, > which is what is used to generate the web

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

Jeff Turner wrote: (changing the topic so people notice its a vote) If I understand correctly, the proposed URL structure is: http://cocoon.apache.org/v1.x/ http://cocoon.apache.org/v2.0/ http://cocoon.apache.org/v2.1/ http://cocoon.apache.org/ -> http://cocoon.apache.org/v2.0 (whatever's the

Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

On 12.Mar.2003 -- 12:54 AM, Jeff Turner wrote: > (changing the topic so people notice its a vote) > > If I understand correctly, the proposed URL structure is: > > http://cocoon.apache.org/v1.x/ > http://cocoon.apache.org/v2.0/ > http://cocoon.apache.org/v2.1/ > http://cocoon.apache.org/ -> >

DO NOT REPLY [Bug 17875] New: - Editing cocoon.xconf causes IllegalStateException

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

[VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)

(changing the topic so people notice its a vote) If I understand correctly, the proposed URL structure is: http://cocoon.apache.org/v1.x/ http://cocoon.apache.org/v2.0/ http://cocoon.apache.org/v2.1/ http://cocoon.apache.org/ -> http://cocoon.apache.org/v2.0 (whatever's the current version)

Re: [ot] switcha

that's not for linux :) you're runnnig OS-X though, aren't you? Nils

Re: Encoding problems

Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set proper content-type header? Vadim

Re: Snapshot links at Cocoon website

On Tue, Mar 11, 2003 at 07:31:10AM -0500, Diana Shannon wrote: > 3. I was really excited about Forrest transition, thinking the > automation would save me all of the above time which I could devote to > docs content. Unfortunately: > - only a few committers participated in the trial run, so it s

Re: form encoding problems

On Mon, 2003-03-03 at 23:00, Jeremy Quinn wrote: [...] > I have got it. This was answered on the users list a while back, sorry > guys. > > Answer, use the SetCharacterEncodingAction in the Pipeline. > > Works with InputModules too. (a bit late to jump into this thread) Are you sure that it wa

Re: Log levels -> DEBUG?

Jeff Turner wrote: On Mon, Mar 10, 2003 at 11:09:09AM -0500, Berin Loritsch wrote: When something breaks, most of the time I have no idea which 'subsystem' is breaking. OTOH, I have a pretty good idea which subsystems are *not* involved. Hence the desire to have DEBUG the default, with progressi

Re: [ot] switcha

Nils Mueller wrote: The only sad thing is there doesn't exist a jdk 1.4 for linux/PPC. time heals all wounds http://www.apple.com/java/ that's not for linux :)

Re: are we ready to move to cocoon.apache.org?

Pier Fumagalli wrote: We're relying on the "xml-site" module to make the CVS updates, we'd have to create our own "cocoon-site" CVS repository to be in line with all other repositories... But I'm thinking as well about the tediousness in rebuilding the site that Diana outlined... It would be probab

Re: [ot] switcha

The only sad thing is there doesn't exist a jdk 1.4 for linux/PPC. time heals all wounds http://www.apple.com/java/ greetz Nils

DO NOT REPLY [Bug 17763] - Internal DTD comments cause invalid XML

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: are we ready to move to cocoon.apache.org?

Pier Fumagalli wrote: "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: Things to do will be: 1) move the existing docs to the cocoon.apache.org virtualhost (please note that the copyright year on the web site is old!) 2) create permanent redirects from the old location to the new one (so that no l

Re: are we ready to move to cocoon.apache.org?

On Tuesday, March 11, 2003, at 07:30 AM, Pier Fumagalli wrote: I would move it in a slightly different way, that will help us to be more flexible wih the new/updated documentation for v2.1 comes out: Why not have this now for alpha/beta docs? It would save some tedious manual synching. There's

Re: Log levels -> DEBUG?

Jeff Turner wrote: When something breaks, most of the time I have no idea which 'subsystem' is breaking. OTOH, I have a pretty good idea which subsystems are *not* involved. Hence the desire to have DEBUG the default, with progressive switching-off of things that ain't broke. Ah, now I see it. I

Re: are we ready to move to cocoon.apache.org?

We're relying on the "xml-site" module to make the CVS updates, we'd have to create our own "cocoon-site" CVS repository to be in line with all other repositories... But I'm thinking as well about the tediousness in rebuilding the site that Diana outlined... It would be probably better to address

RE: are we ready to move to cocoon.apache.org?

Is updating the docs then the same procedure than before (updating from cvs)? Carsten > -Original Message- > From: Pier Fumagalli [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 1:30 PM > To: [EMAIL PROTECTED] > Subject: Re: are we ready to move to cocoon.apache.org? > > > "Stef

Re: Snapshot links at Cocoon website

On Tuesday, March 11, 2003, at 05:32 AM, Pier Fumagalli wrote: I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Yes, but at that point we'll have to re-build the site once again... Ok, we shouldn't be so limited in rebuilding the site as

Re: Encoding problems

On Tuesday, March 11, 2003, at 11:48 AM, Stefano Mazzocchi wrote: The new webapp welcome page contains a copyright character which is not encoded as the default HTML entity © or the usual &xxx; char, but it's directly copied in the proper encoding. Many thanks for your analysis and confirmati

Re: are we ready to move to cocoon.apache.org?

"Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > Things to do will be: > > 1) move the existing docs to the cocoon.apache.org virtualhost (please > note that the copyright year on the web site is old!) > > 2) create permanent redirects from the old location to the new one (so > that no links are

Re: Log levels -> DEBUG?

On Mon, Mar 10, 2003 at 11:09:09AM -0500, Berin Loritsch wrote: > Jeff Turner wrote: > >On Mon, Mar 10, 2003 at 08:52:11AM -0500, Berin Loritsch wrote: > > > >>Jeff Turner wrote: > >> > >> > From src/webapp/WEB-INF/logkit.xconf: > >>> > >>> > >>> > >>>revision 1.13 >

Re: DO NOT REPLY [Bug 17673] - sendPage function in Flow causesan NPE.

[I was sure I had already replied to this message, but I cannot see i in the list.] Carsten Ziegeler wrote: Addition: It should be in the redirector, I will commit a fix in three minutes, can you please test it? Carsten It works. Nice job, thank you. Ugo

Re: DO NOT REPLY [Bug 17673] - sendPage function in Flow causesan NPE.

Carsten Ziegeler wrote: Addition: It should be in the redirector, I will commit a fix in three minutes, can you please test it? Carsten Tested, and it passes with flying colors. Well, at least my application now works again with the latest CVS code, so I assume everything is OK ;-). Thank you fo

are we ready to move to cocoon.apache.org?

Things to do will be: 1) move the existing docs to the cocoon.apache.org virtualhost (please note that the copyright year on the web site is old!) 2) create permanent redirects from the old location to the new one (so that no links are broken) anything else? Stefano.

Re: DOMStreamer DOM 1 support?

On Tue, Mar 11, 2003 at 12:39:18PM +0100, Bruno Dumon wrote: > On Tue, 2003-03-11 at 09:15, Jeff Turner wrote: > > On Tue, Mar 11, 2003 at 08:14:21AM +0100, Bruno Dumon wrote: > > > On Tue, 2003-03-11 at 07:37, Jeff Turner wrote: > > > > Probably a question for Bruno.. > > > > > > > > The Namespac

Encoding problems

The new webapp welcome page contains a copyright character which is not encoded as the default HTML entity © or the usual &xxx; char, but it's directly copied in the proper encoding. The offending char is contained in the welcome.xslt stylesheet that is encoded as ISO-8859-1. The pipeline does

Re: DOMStreamer DOM 1 support?

On Tue, 2003-03-11 at 09:15, Jeff Turner wrote: > On Tue, Mar 11, 2003 at 08:14:21AM +0100, Bruno Dumon wrote: > > On Tue, 2003-03-11 at 07:37, Jeff Turner wrote: > > > Probably a question for Bruno.. > > > > > > The NamespaceNormalizingDOMStreamer doesn't support DOM 1 nodes, which > > > means th

FYI: Java 1.4.1 final for MacOSX

Dear All, My apologies to those for whom this is irrelevant Apple have today released the Final of Java 1.4.1 for MacOSX, get it via the Software Update System Preference pane. At last we are no longer second class Java citizens ;) regards Jeremy

RE: Snapshot links at Cocoon website

> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Ok, it's working here as well, but shouldn't the links go > to cocoon-2.1? Good question ... I would link to http://xml.apache.org/cocoon/mirror.cgi#nightly but this would need a rebuild of the complete site (as Pier pointed out). But maybe th

RE: Snapshot links at Cocoon website

Ok, it's working here as well, but shouldn't the links go to cocoon-2.1? Carsten > -Original Message- > From: Reinhard Pötz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 11:55 AM > To: [EMAIL PROTECTED] > Subject: RE: Snapshot links at Cocoon website > > > > That is the only o

DO NOT REPLY [Bug 17594] - WebSphere redirect bug

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: Snapshot links at Cocoon website

> That is the only occurrence of the word "xml-cocoon2" on the > server, all other problems are client-cache related... I checked it again and now the link is correct. Probably a proxy server issue because client caching is turned off in all my browsers. Reinhard

Re: Snapshot links at Cocoon website

On 11/3/03 7:32, "Reinhard Pötz" <[EMAIL PROTECTED]> wrote: >> From: Pier Fumagalli [mailto:[EMAIL PROTECTED] >> >> On 10/3/03 7:42, "Carsten Ziegeler" <[EMAIL PROTECTED]> wrote: >> >>> b) Let's get the nightly build working asap >> >> Carsten, are you talking about the nightly builds (GUMP) or

Re: Ripping the heart out

On 11/3/03 7:26, "Carsten Ziegeler" <[EMAIL PROTECTED]> wrote: > Great! Thanks! > > This decreases our problem counter - but the links on our homepage > are still refering to xml-cocoon2 cvs snapshots. This must be > fixed as well. I replaced _all_ occurences of the word "xml-cocoon2"... This is

Re: cvs commit: cocoon-2.1 build.xml

Bernhard Huber wrote: hi, just two open issues: + + + + + + may be you have forgotten to add webapp/stylesheets directory? No, I didn't forget, I'm going to do it later today (I'm working on polishing and improving the error messaging pipelines + stylesheets

Re: Rhino with continuations cvs

Christopher Oliver wrote: Just wanted to let people know that thanks to Steven Noels and Ovidiu the Rhino interpreter with continuations recently got a CVS repository at cocoondev.org: http://cvs.cocoondev.org/cgi-bin/viewcvs.cgi/rhino1_5R4pre That's very good. BTW, do you have any news on the

Re: live site update complete

Vadim Gritsenko wrote: Pier Fumagalli wrote: "Diana Shannon" <[EMAIL PROTECTED]> wrote: I updated the live site docs, with changes primarily reflecting the new cvs setup. A big thanks to Pier for the new cvs setup and **particularly** for making such a thorough update of all relevant docs in b

DO NOT REPLY [Bug 17806] - [PATCH] jars.xml has incorrect reference to excalibur-xmlutil-20030306.jar

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 12115] - [PATCH]NPE in AbstractCachingProcessingPipeline.java

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 12115] - [PATCH]NPE in AbstractCachingProcessingPipeline.java

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

  1   2   >