RE: svn commit: rev 55618 - cocoon/trunk/src/blocks/axis/conf

Thanks Unico! Carsten > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 6:59 PM > To: [EMAIL PROTECTED] > Subject: svn commit: rev 55618 - cocoon/trunk/src/blocks/axis/conf > > Author: unico > Date: Tue Oct 26 09:58:44 2004 > New

Re: HtmlCleaningConvertor

Bruno Dumon wrote: On Mon, 2004-10-25 at 18:38 +0200, Reinhard Poetz wrote: While browsing Daisy I saw a very interesting cForms extension in Daisy: the HtmlCleaningConvertor. Are there any plans to move it to Cocoon? Didn't think of that yet. Keeping it with Daisy would make it follow Daisy rele

Re: [RT] doco lite?

Le 26 oct. 04, à 22:56, Frédéric Glorieux a écrit : ...T2. Build an index with Lucene, triggered via SVN post-commit hooks, uses a live Cocoon instance to generate an easy to index XML document for Lucene. Include metadata fields as mentioned in G2 above, generated from (enhanced as compared to

Re: [RT] doco lite?

Le 26 oct. 04, à 22:34, Upayavira a écrit : ...So you'd use HEAD or whatever to view the latest commit, and the public would see the "current-docs" tag. That could work. But would we want the HEAD to be password protected, or in some way hidden so that it doesn't get regularly viewed when it isn

Re: [RT] doco lite?

Le 26 oct. 04, à 21:56, Jorg Heymans a écrit : ...1)Does all this actually make the documentation any better? The content, would not immediately be improved of course. But simplifying the docs publishing process is an enabler for improving the docs. 2)Should any effort towards documentation ATM

Re: Let's deprecate the PHP block

David Crossley wrote: So when a real, potentially damaging, issue arises we will have no way to sensibly handle it. It has been working fine so far and I see no evidence of things changing. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature

How to make things better

Luigi Bai wrote: If you have ideas on how to make it better, we are wide open to suggestions. Okay, assuming your sincerity - what is the current method for committers to find/fix/close issues in Bugzilla? there is no codified method. Basically, one those patches/fixes/bugs that are promoted by

Re: [RT] doco lite?

Upayavira wrote: > Bertrand Delacretaz wrote: > > Upayavira a écrit : > > > >> ...The thing you seem to have missed is the staging process. If I > >> have written an xdoc, I want to see that as HTML, on a staging > >> server, before I actually publish it. After all, the XML might not > >> even b

Cocoon read-only (ex: CD-ROM) add ${context-work} parameter to logkit.xconf from CocoonServlet.java

Hello, For sysadmin, it may be important for the cocoon servlet to be totally read-only, even logs. I used to try to run a same cocoon in parallel in different servlet contexts (same JVM, same tomcat, different URIs). Logs were quite funny to read but a bit broken. For a fast patch, I added 2 l

Re: Let's deprecate the PHP block

Stefano Mazzocchi wrote: > Bertrand Delacretaz wrote: > > > > I see David's point though, using [VOTE] in subject (and [PROPOSAL] > > maybe) helps in not missing stuff that's happening. > > > > But I like our +1 way of saying "me? I like it" even if outside of a > > vote - it's part of our "slan

Re: handling Bugzilla backlog (Was: Let's deprecate the PHP block)

On Tue, 27 Oct 2004, David Crossley wrote: Luigi Bai wrote: Stefano Mazzocchi wrote: Maybe it is more precise to say "When shit works /mostly/ well...". The presence of a large number of outstanding Bugzilla issues, especially ones with [PATCH]es attached, implies that things work well for committe

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

This seemed to be related to the removal of instrumentation from the axis block. Should be fixed now. -- Unico Thanks a lot. This is working well for me. I'm glad to delete my ugly patches. -- Frédéric Glorieux (ingénieur documentaire, AJLSM)

handling Bugzilla backlog (Was: Let's deprecate the PHP block)

Luigi Bai wrote: > Stefano Mazzocchi wrote: > >> > >> Maybe it is more precise to say "When shit works /mostly/ well...". The > >> presence of a large number of outstanding Bugzilla issues, especially ones > >> with [PATCH]es attached, implies that things work well for committers, less > >> wel

Re: svn commit: rev 55059 - in cocoon/trunk/src/java/org/apache/cocoon: . components/flow

Il giorno 19/ott/04, alle 15:11, [EMAIL PROTECTED] ha scritto: Removed: cocoon/trunk/src/java/org/apache/cocoon/components/flow/ InterpreterSelector.java This class is referred to in the javaflow block's tests. See JavaFlowTestCase.xtest: shorthand="flow-interpreters" de

RE: [RT] doco lite?

Jorg Heymans wrote: > 2)Should any effort towards documentation ATM go into improving its > *quality* or improving its > {searchability|updateability|scaleability|auto-generateability} > > WDYT? Personally, I think that Cocoon has a lot of good documentation, but poorly/inconsistently organis

Re: [RT] doco lite?

Upayavira wrote: GOALS G4. Make submitting documentation a more straight forward process. I haven't yet looked at the ins and outs of the xdocs, but I know from the times I tried to find the documentation in the checked out tree that I was unable to figure out how it worked. TOOLS / TECHNIQUES

Re: Let's deprecate the PHP block

On Tue, 26 Oct 2004, Stefano Mazzocchi wrote: Luigi Bai wrote: On Tue, 26 Oct 2004, Stefano Mazzocchi wrote: forth: some of us spend a great amount of their life trying to come up with strategies that avoid the use of those rules, and understand how complex groups form and dissolve, how innovatio

Re: Let's deprecate the PHP block

Stefano Mazzocchi wrote: ... If you have ideas on how to make it better, we are wide open to suggestions. Making the Subject match the content of this thread would be a good start. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussion

Re: Let's deprecate the PHP block

Luigi Bai wrote: On Tue, 26 Oct 2004, Stefano Mazzocchi wrote: forth: some of us spend a great amount of their life trying to come up with strategies that avoid the use of those rules, and understand how complex groups form and dissolve, how innovation happens and how community fractures can be

Re: Let's deprecate the PHP block

On Tue, 26 Oct 2004, Stefano Mazzocchi wrote: forth: some of us spend a great amount of their life trying to come up with strategies that avoid the use of those rules, and understand how complex groups form and dissolve, how innovation happens and how community fractures can be avoided. When shi

Re: [RT] doco lite?

G3. Index the latest version of the docs, including structured fields (keywords, target audience, components mentioned, etc), to implement "prepared queries" (as links, simply) to improve our docs' accessibility It seems a good occasion to provide a better LuceneTransformer implementation for

Re: Let's deprecate the PHP block

I'm trying really really really hard not to reply to this but I can't. Frédéric Glorieux wrote: For computing, you are really incredible guys, but for politics, I'm sorry to say that but you are "reinventing the wheel". Rules are not "bureaucratic" but the only way to have a stable democracy, whi

Re: [RT] doco lite?

Bertrand Delacretaz wrote: Le 26 oct. 04, à 21:20, Upayavira a écrit : ...The thing you seem to have missed is the staging process. If I have written an xdoc, I want to see that as HTML, on a staging server, before I actually publish it. After all, the XML might not even be valid, or there might

Re: [RT] doco lite?

Jorg Heymans wrote: Bertrand Delacretaz wrote: GOALS G1. Generate our docs and website dynamically, directly from the SVN repository accessed over http G2. Give access to older versions of the docs using standard SVN mechanisms (tags etc) G3. Index the latest version of the docs, including struc

Re: Let's deprecate the PHP block

One trouble is that Cocoon does not yet have any project guidelines. Another trouble is that people seem to use the +1 thing even when a vote is not happening. The proposal phase for the discussion, then the vote phase for the decision, is an Apache way to get things done efficiently. We forget th

Re: [RT] doco lite?

Bertrand Delacretaz wrote: GOALS G1. Generate our docs and website dynamically, directly from the SVN repository accessed over http G2. Give access to older versions of the docs using standard SVN mechanisms (tags etc) G3. Index the latest version of the docs, including structured fields (keywo

Re: HtmlCleaningConvertor

On Mon, 2004-10-25 at 18:38 +0200, Reinhard Poetz wrote: > While browsing Daisy I saw a very interesting cForms extension in Daisy: the > HtmlCleaningConvertor. Are there any plans to move it to Cocoon? Didn't think of that yet. Keeping it with Daisy would make it follow Daisy releases, which is

Re: Let's deprecate the PHP block

Torsten Curdt wrote: +1 ...I guess noone really used it anyway -- Torsten I really really really tried when I first moved to cocoon :( JD

Re: [RT] doco lite?

Le 26 oct. 04, à 21:23, Scherler, Thorsten a écrit : To understand it right you do not want online editing, workflow,... right? Why not, but separating this concern from the publishing process makes the problem easier to tackle IMHO. -Bertrand smime.p7s Description: S/MIME cryptographic signat

Re: [RT] doco lite?

Le 26 oct. 04, à 21:20, Upayavira a écrit : ...The thing you seem to have missed is the staging process. If I have written an xdoc, I want to see that as HTML, on a staging server, before I actually publish it. After all, the XML might not even be valid, or there might be mistakes. I need to be

Re: [RT] doco lite?

To understand it right you do not want online editing, workflow,... right? Sounds like a nice start for doco. Small, slim and lite. ;-) thorsten Antonio Gallardo escribió: Bertrand Delacretaz dijo: Recent discussions here, along with David's "ASF-wide documentation staging and publishing" post to i

Re: [RT] doco lite?

Bertrand Delacretaz wrote: Recent discussions here, along with David's "ASF-wide documentation staging and publishing" post to infrastructure@ made me think about this, in a "there must be an easier way" mood. I'm not ready to discuss this on infrastructure@ though, it feels safer here ATM ;-)

Re: [RT] doco lite?

Bertrand Delacretaz dijo: > Recent discussions here, along with David's "ASF-wide documentation > staging and publishing" post to infrastructure@ made me think about > this, in a "there must be an easier way" mood. I'm not ready to discuss > this on infrastructure@ though, it feels safer here ATM

Re: Let's deprecate the PHP block

+1 ...I guess noone really used it anyway -- Torsten

[GUMP@brutus]: Project cocoon (in module cocoon) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 56 pr

Re: Cocoon and JDK 1.5

Hi Bert: Thnks for the effort. Please see this: http://issues.apache.org/bugzilla/show_bug.cgi?id=30883 I think the next release is soon. Best Regards, Antonio Gallardo

[RT] doco lite?

Recent discussions here, along with David's "ASF-wide documentation staging and publishing" post to infrastructure@ made me think about this, in a "there must be an easier way" mood. I'm not ready to discuss this on infrastructure@ though, it feels safer here ATM ;-) The apparently realistic p

Re: Howto drive response payload directly

On Oct 26, 2004, at 3:46 AM, Vadim Gritsenko wrote: Ugo Cei wrote: Il giorno 26/ott/04, alle 08:54, Leszek Gawron ha scritto: Mark Lundquist wrote: Hi, I have a Java object persisted using Hibernate... it contains an image (java.sql.Blob) that I need to serve. I can get the object in flowscript,

Re: Let's deprecate the PHP block

Le 26 oct. 04, à 18:19, Sylvain Wallez a écrit : ...Yup. You can even have a T-Shirt with it: http://www.cafepress.com/meepzor.10338499 Wow. +1 ;-) -Bertrand smime.p7s Description: S/MIME cryptographic signature

Re: svn commit: rev 55619 - in cocoon/branches/BRANCH_2_1_X/src: test/anteater webapp/samples/test/reader-mime-type

Unico Hommes wrote: Now only one release blocker remains: NPE in AbstractEnvironment.release() No, not exactly. As I see it, ResourceReader should return Source's mimeType in this particular case, as per: public String getMimeType() { Context ctx = ObjectModelHelper.getContext(objectM

Re: svn commit: rev 55619 - in cocoon/branches/BRANCH_2_1_X/src: test/anteater webapp/samples/test/reader-mime-type

Now only one release blocker remains: NPE in AbstractEnvironment.release() -- Unico [EMAIL PROTECTED] wrote: Author: unico Date: Tue Oct 26 10:07:04 2004 New Revision: 55619 Modified: cocoon/branches/BRANCH_2_1_X/src/test/anteater/reader-mime-type.xml cocoon/branches/BRANCH_2_1_X/src/webapp/sa

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

This seemed to be related to the removal of instrumentation from the axis block. Should be fixed now. -- Unico Tim Larson wrote: On Tue, Oct 26, 2004 at 01:49:24PM +0200, Unico Hommes wrote: On 24-okt-04, at 13:47, Unico Hommes wrote: The Request interface itself does not have getInputStr

Re: Let's deprecate the PHP block

Bertrand Delacretaz wrote: Le 26 oct. 04, à 17:41, Stefano Mazzocchi a écrit : ..Bah, burocrats. ;-) I see David's point though, using [VOTE] in subject (and [PROPOSAL] maybe) helps in not missing stuff that's happening. But I like our +1 way of saying "me? I like it" even if outside of a vote

Re: Let's deprecate the PHP block

Bertrand Delacretaz wrote: Le 26 oct. 04, à 17:41, Stefano Mazzocchi a écrit : ..Bah, burocrats. ;-) I see David's point though, using [VOTE] in subject (and [PROPOSAL] maybe) helps in not missing stuff that's happening. But I like our +1 way of saying "me? I like it" even if outside of a vote

DO NOT REPLY [Bug 30040] - JS 'popups' are rendered behind select lists and applets.

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://issues.apache.org/bugzilla/show_bu

Re: Let's deprecate the PHP block

On 26.10.2004 15:11, Antonio Gallardo wrote: Let's deprecate the PHP block for the remainder of our 2.1.X releases and then dump it in 2.2. If people want to "use" PHP with Cocoon, the best solution is to just use a FileGenerator and an http:// URL. Seems we are alredy voting on that. Here is min

Re: Let's deprecate the PHP block

Le 26 oct. 04, à 17:41, Stefano Mazzocchi a écrit : ..Bah, burocrats. ;-) I see David's point though, using [VOTE] in subject (and [PROPOSAL] maybe) helps in not missing stuff that's happening. But I like our +1 way of saying "me? I like it" even if outside of a vote - it's part of our "slang" I

Re: Let's deprecate the PHP block

Stefano Mazzocchi wrote: Oh, c'mon, we have a gazillion +1 and no -1, go ahead and deprecate it. It's not like we can't reverse the thing if a -1 shows up. Bah, burocrats. Sir, I'll have to ask you to file a formal complaint, and you can expect a response in 6 to 8 weeks. :) :) Tony

Re: Let's deprecate the PHP block

Tony Collen wrote: Bertrand Delacretaz wrote: +1, I agree with the formal vote but if you start it by counting all the +1s here we don't need to vote again. Alright, well I guess I phrased my message as a pseudo-vote, so the confusion is my fault! Anyway, I'l count the existing votes as if it w

Re: Let's deprecate the PHP block

David Crossley wrote: No, it is not bureaucratic. It is about efficiency. That's what bureaucrats always say ;-) -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature

Re: Let's deprecate the PHP block

Bertrand Delacretaz wrote: +1, I agree with the formal vote but if you start it by counting all the +1s here we don't need to vote again. Alright, well I guess I phrased my message as a pseudo-vote, so the confusion is my fault! Anyway, I'l count the existing votes as if it were an official vote

RE: Portal - coplet instance data attributes

I'm noticing that the mapping file for copletinstancedata specifies that AttributesFieldHandler should be used. I haven't used Castor much, but it seems I could make a simple change to that class to make sure it gets only the attributes from copletinstancedata when necessary. If so, would that fi

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

On Tue, Oct 26, 2004 at 01:49:24PM +0200, Unico Hommes wrote: > On 24-okt-04, at 13:47, Unico Hommes wrote: > >The Request interface itself does not have getInputStream method, only > >HttpRequest does. So first step would be to add getInputStream method > >to the Request and then add it to FOM.

Re: VMWare host for us @apache.org

David Crossley wrote: David Crossley wrote: Upayavira wrote: David Crossley wrote: The docs aspect needs lots of consideration. If Cocoon wants to continue using Forrest, then we would like help to implement our plans for the Forrestbot and staging server for reviewing docs prior to publication. W

DO NOT REPLY [Bug 29360] - precompile xsp's without starting URI

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: VMWare host for us @apache.org

David Crossley wrote: > Upayavira wrote: > > David Crossley wrote: > > > > >The docs aspect needs lots of consideration. If Cocoon wants to > > >continue using Forrest, then we would like help to implement > > >our plans for the Forrestbot and staging server for reviewing > > >docs prior to publica

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: Let's deprecate the PHP block

Tony Collen dijo: > Let's deprecate the PHP block for the remainder of our 2.1.X releases > and then dump it in 2.2. If people want to "use" PHP with Cocoon, the > best solution is to just use a FileGenerator and an http:// URL. Seems we are alredy voting on that. Here is mine: +1 NOTE: Please

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: Let's deprecate the PHP block

Vadim Gritsenko wrote: > David Crossley wrote: > > Bertrand Delacretaz wrote: > > > >>Reinhard Poetz a écrit : > >> > >>>Tony Collen wrote: > >>> > ...Let's deprecate the PHP block for the remainder of our 2.1.X > releases and then dump it in 2.2. If people want to "use" PHP with >

Re: Howto drive response payload directly

Ugo Cei wrote: Il giorno 26/ott/04, alle 08:54, Leszek Gawron ha scritto: Mark Lundquist wrote: Hi, I have a Java object persisted using Hibernate... it contains an image (java.sql.Blob) that I need to serve. I can get the object in flowscript, now I just need to stream out this data (e.g. "imag

Re: Let's deprecate the PHP block

Tony Collen wrote: ... Let's deprecate the PHP block for the remainder of our 2.1.X releases and then dump it in 2.2. If people want to "use" PHP with Cocoon, the best solution is to just use a FileGenerator and an http:// URL. I had written a similar mail a loong time ago, so I only find it nat

Re: Let's deprecate the PHP block

David Crossley wrote: Bertrand Delacretaz wrote: Reinhard Poetz a écrit : Tony Collen wrote: ...Let's deprecate the PHP block for the remainder of our 2.1.X releases and then dump it in 2.2. If people want to "use" PHP with Cocoon, the best solution is to just use a FileGenerator and an http://

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

On 24-okt-04, at 13:47, Unico Hommes wrote: On 24-okt-04, at 1:38, Frédéric Glorieux wrote: Hello, Like explained in another thread, I'm trying to implement a PUT binaries in the webdav/davmap demo. I wrote a simple "RequestReader" like waited in the sitemap sample, it works well for httpRequest,

Re: Let's deprecate the PHP block

Bertrand Delacretaz wrote: > Reinhard Poetz a écrit : > > > Tony Collen wrote: > >> ...Let's deprecate the PHP block for the remainder of our 2.1.X > >> releases and then dump it in 2.2. If people want to "use" PHP with > >> Cocoon, the best solution is to just use a FileGenerator and an > >>

RE: Gump help requested

Yes, it's ant-contrib. Thanks for the patch, it's applied. Carsten > -Original Message- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 12:33 PM > To: [EMAIL PROTECTED] > Subject: Gump help requested > > > Gang, > > I am trying to get Gump to build

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Gump help requested

Gang, I am trying to get Gump to build Cocoon. In the build script there is a element. I guess that it comes from the ant-contrib package. If so, the following patch would be needed for gump.xml in the 2.2 branch. Cheers Niclas -- +--//---+ / http://www.bali.ac

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

You can find some samples in: http://cvs.apache.org/viewcvs.cgi/cocoon/trunk/src/blocks/scratchpad/samples/module-source/?root=Apache-SVN And some documentation in: http://wiki.apache.org/cocoon/ModuleSource There are docu and samples for XModuleSource also: http://cvs.apache.org/viewcvs.cgi/co

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: Let's deprecate the PHP block

Le 26 oct. 04, à 11:33, Reinhard Poetz a écrit : Tony Collen wrote: ...Let's deprecate the PHP block for the remainder of our 2.1.X releases and then dump it in 2.2. If people want to "use" PHP with Cocoon, the best solution is to just use a FileGenerator and an http:// URL... +1 too. Could you

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: Let's deprecate the PHP block

Tony Collen wrote: To my knowledge, the PHPGenerator hasn't worked for quite some time. In all the time I've been working with Cocoon, I have never seen it work correctly. However, I believe the problem is within the PHP Servlet itself, which, if you do some research, tons of people have had p

[GUMP@brutus]: Project cocoon (in module cocoon) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 56 pr

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

Vadim Gritsenko wrote: Sylvain Wallez wrote: But we have to define the behavior of getInputStream for environments where it has no meaning (e.g. background env, It can be initialized with java.io.InputStream (File, byte array), or null. If null, throw exception. sitemap source, cocoonbean I beli

Re: Let's deprecate the PHP block

Tony Collen wrote: To my knowledge, the PHPGenerator hasn't worked for quite some time. In all the time I've been working with Cocoon, I have never seen it work correctly. However, I believe the problem is within the PHP Servlet itself, which, if you do some research, tons of people have had p

DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?

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://issues.apache.org/bugzilla/show_bu

Re: getInputStream() in FOM_Cocoon.FOM_Request ?

Frédéric Glorieux wrote: Request reader and this works as well. This writing is nice, I like it. Is there some more samples of those things ? You can find some samples in: http://cvs.apache.org/viewcvs.cgi/cocoon/trunk/src/blocks/scratchpad/samples/module-source/?root=Apache-SVN And some docume

Re: Let's deprecate the PHP block

On Mon, 25 Oct 2004, Tony Collen wrote: Let's deprecate the PHP block for the remainder of our 2.1.X releases and then dump it in 2.2. If people want to "use" PHP with Cocoon, the best solution is to just use a FileGenerator and an http:// URL. +1 -- Giacomo Pati Otego AG, Switzerland - http://w

DO NOT REPLY [Bug 31813] - [Sample] DreamTeam (dependent widgets in a repeater)

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://issues.apache.org/bugzilla/show_bu

Re: Questions to be answered for link request - V2

On Fri, 22 Oct 2004, Bertrand Delacretaz wrote: > Le 22 oct. 04, ΰ 15:49, Hunsberger, Peter a ιcrit : > > ...Would an "Intranet applications" section also make sense? As I see > > it, > > this list would be a list of organizations and applications with a > > brief > > description of the applica

RE: Portal - coplet instance data attributes

Hmm, I really can't remember everything. Now one problem was that if you save the objects to XML, you can't save all available attributes for the instance. You have to filter and only save the attributes that are part of the instance and not those of the coplet data. An additional problem is remov

Re: Howto drive response payload directly

Il giorno 26/ott/04, alle 08:54, Leszek Gawron ha scritto: Mark Lundquist wrote: Hi, I have a Java object persisted using Hibernate... it contains an image (java.sql.Blob) that I need to serve. I can get the object in flowscript, now I just need to stream out this data (e.g. "image.getBinaryStre