Re: Sitemap problem... help! :-)

Mark Lundquist wrote: OK, I figured out the problem (qv. http://marc.theaimsgroup.com/?t=11070194514&r=1&w=2). I had one matcher in the root sitemap that handled all continuation URIs, even those that are generated from pipelines in subsitemaps. So apparently, the context for the redirector

Re: [announcement/proposal] Moving Linotype out of Cocoon

Stefano Mazzocchi wrote: For this reason, I propose that we discontinue the distribution of Linotype inside cocoon as a block, by deprecating it in the next 2.1.x release and by removing it alltogether in 2.2 Of course, the project will remain an open development project and I will welcome peo

Re: [announcement/proposal] Moving Linotype out of Cocoon

Stefano Mazzocchi wrote: As some of you know, my personal blog runs on this software called "Linotype" that I wrote for myself (on top of cocoon) and then donated to the project to show an example of how simple it was to build even a real-life webapp with flow. For this reason, Linotype ended b

SVN behaviour with "Id" keyword

Hi all, I found today some interesting things regarding how SVN handles keyword expansion. In order to do some merging between 2.1 and 2.2 on CForms code, I wrote a small shell script that replaces all expanded "$Id $" keywords by the unexpanded "$Id$" in order to use the nice Eclipse diff

Re: Sitemap problem... help! :-)

Sylvain Wallez wrote: Mark Lundquist wrote: OK, I figured out the problem (qv. http://marc.theaimsgroup.com/?t=11070194514&r=1&w=2). I had one matcher in the root sitemap that handled all continuation URIs, even those that are generated from pipelines in subsitemaps. So apparently, the cont

[GUMP@brutus]: Project cocoon-block-template (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-block-template has an issue affecting its community integration. This issu

[GUMP@brutus]: Project cocoon-block-forms (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-block-forms has an issue affecting its community integration. This issue a

Re: SVN behaviour with "Id" keyword

On Sunday 30 January 2005 18:21, Sylvain Wallez wrote: > So I came to the conclusion that SVN is smart (too much maybe) and only > replaces the content of an expanded keyword if this content matches some > well-defined and strict pattern. or, are you sure that the svn:keyword attribute is set for

Re: [announcement/proposal] Moving Linotype out of Cocoon

Anyway, what do you think? +0.5 I don't mind where it's being hosted but let us know where we can help :) cheers -- Torsten signature.asc Description: OpenPGP digital signature

Re: SVN behaviour with "Id" keyword

Niclas Hedhman wrote: On Sunday 30 January 2005 18:21, Sylvain Wallez wrote: So I came to the conclusion that SVN is smart (too much maybe) and only replaces the content of an expanded keyword if this content matches some well-defined and strict pattern. or, are you sure that the svn:keywor

Re: [announcement/proposal] Moving Linotype out of Cocoon

On 30.01.2005 05:37, Stefano Mazzocchi wrote: For this reason, I propose that we discontinue the distribution of Linotype inside cocoon as a block, by deprecating it in the next 2.1.x release and by removing it alltogether in 2.2 +1 Joerg

Re: Sitemap problem... help! :-)

Leszek Gawron wrote: Sylvain Wallez wrote: Mark Lundquist wrote: OK, I figured out the problem (qv. http://marc.theaimsgroup.com/?t=11070194514&r=1&w=2). I had one matcher in the root sitemap that handled all continuation URIs, even those that are generated from pipelines in subsitemaps. So

Re: [announcement/proposal] Moving Linotype out of Cocoon

Sounds fine. (not +1 because this isn't a vote and one isn't needed). I look forward to test-driving the new improved version, and the potential for further symbiosis with MIT & W3C Geoff On Sat, 29 Jan 2005 23:37:57 -0500, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > For this reason, I propo

DO NOT REPLY [Bug 32987] - [PATCH] Small fix that throws meaningful configuration exception on input module not found before NPE is thrown few lines lower in the code.

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 32987] - [PATCH] Small fix that throws meaningful configuration exception on input module not found before NPE is thrown few lines lower in the code.

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: Sitemap problem... help! :-)

On Jan 30, 2005, at 3:07 AM, Leszek Gawron wrote: You should have errors in your log files when getting this kind of InvalidContinuationException: if (!kont.interpreterMatches(interpreterId)) { getLogger().error( "WK: Continuation (" + kont.getId()

Re: Sitemap problem... help! :-)

On Jan 30, 2005, at 5:21 AM, Sylvain Wallez wrote: I don't think we should go that far: IMO, having an exception with a clear reason message is enough, as it shows that there is a bug in the application that needs to be fixed. Mark had no such exception, and that's why he spent much time to find

[RT] input-modules in the sitemap

Am I the only one that is bugged by the fact that you have to add the input modules in the cocoon.xconf while the sitemap components go in the sitemap? -- Stefano.

Re: [RT] input-modules in the sitemap

Stefano Mazzocchi wrote: Am I the only one that is bugged by the fact that you have to add the input modules in the cocoon.xconf while the sitemap components go in the sitemap? Recently there was a discussion about FOM and input modules: http://marc.theaimsgroup.com/?t=11065482741&r=1&w=2, i

Re: [RT] input-modules in the sitemap

Stefano Mazzocchi wrote: Am I the only one that is bugged by the fact that you have to add the input modules in the cocoon.xconf while the sitemap components go in the sitemap? As part of the stuff Sylvain and Carsten recently did I thought we discussed putting all "definitions" in the block's

DO NOT REPLY [Bug 33178] - Mounting a sitemap with pass-through alters resolveURI

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: [RT] input-modules in the sitemap

Stefano Mazzocchi wrote: Am I the only one that is bugged by the fact that you have to add the input modules in the cocoon.xconf while the sitemap components go in the sitemap? You can do it right now. is handled exactly as an xconf file to feed the service manager. And since components don't