trunk build broken (Was: how to list all sitemap components)

The Cocoon SitemapTask in trunk is suddenly throwing a wobbly. - ... Building component docs from blocks. Collecting sitemap components info BUILD FAILED /opt/cocoon-trunk/tools/targets/docs-build.xml:55: Sitemap component org.apache.cocoon.generation.HTMLGenerator does not implem

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

On Jan 10, 2005, at 10:35 AM, Daniel Fagerstrom wrote: Glen Ezkovich wrote: I've been thinking about why one would want to isolate a blocks flowscripts from other blocks. So far I see two reasons: 1.) some flowscript functions are simply helper functions and should not be directly callled.

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: [RT] Implementation of VPCs and "multi-relative" source resolving (long)

A somewhat late answer ;) But I have spent some more thinking on this during the discussion about exporting flowscript functions from blocks. Sylvains original mail can be found in http://marc.theaimsgroup.com/?t=11006456093&r=1&w=2. What I will discuss is rather subtle and involved stuff,

[CLI] Problem with XSP compilation

Hi Cocooners, First, I wish you a great year and may all your projects (professionnal but also personal) be accomplished ! Then, I would like to explain my pb. I developped a small app that creates a cli.xconf file with all XSP of a webapp. Then when I launch the Cocoon CLI, it stops without an e

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Glen Ezkovich wrote: I've been thinking about why one would want to isolate a blocks flowscripts from other blocks. So far I see two reasons: 1.) some flowscript functions are simply helper functions and should not be directly callled. 2.) a block may use its own classloader and therefore

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Reinhard Poetz wrote: Daniel Fagerstrom wrote: Reinhard Poetz wrote: Daniel Fagerstrom wrote: A somewhat unrelated thing that we have to think about is the web continuations created in the block, do we need to shield the web continuations created in the block or not? shielded from what? The

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Daniel Fagerstrom wrote: Reinhard Poetz wrote: Daniel Fagerstrom wrote: A somewhat unrelated thing that we have to think about is the web continuations created in the block, do we need to shield the web continuations created in the block or not? shielded from what? The user should be able to r

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Reinhard Poetz wrote: Daniel Fagerstrom wrote: A somewhat unrelated thing that we have to think about is the web continuations created in the block, do we need to shield the web continuations created in the block or not? shielded from what? The user should be able to resume a continuation cre

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

On Jan 10, 2005, at 9:32 AM, Reinhard Poetz wrote: Torsten Curdt wrote: So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Glen Ezkovich wrote: On Jan 10, 2005, at 9:07 AM, Torsten Curdt wrote: So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by t

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Torsten Curdt wrote: So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by the callee. Yes, and when sendPageAndWait returns

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

On Jan 10, 2005, at 9:07 AM, Torsten Curdt wrote: So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by the callee. Yes, and w

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

I've been thinking about why one would want to isolate a blocks flowscripts from other blocks. So far I see two reasons: 1.) some flowscript functions are simply helper functions and should not be directly callled. 2.) a block may use its own classloader and therefore possibly use different ve

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by the callee. Yes, and when sendPageAndWait returns the calling blocks fl

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

On Jan 10, 2005, at 7:24 AM, Reinhard Poetz wrote: So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait? because this is done in the called block, not by the callee. Yes, and w

Re: ANN: [portal] New CachingPortletAdapter

DURDINA Michal wrote: I checked Pluto 1.0.1-rc1 (and also trunk) and the result is: pluto portal (/portal) does not implement caching yet. The portlet.xml expiration-cache element is parsed in PortletDefinitionImpl but never read (checked with Eclipse -> References). The same is valid for cocoon

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Daniel Fagerstrom wrote: Reinhard Poetz wrote: Daniel Fagerstrom wrote: A question here is what flowscript functions that should be exported from a block. I would prefer to explictly enumerate the functions and possibly whole scripts that are exported rather than exporting everything in the ma

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Glen Ezkovich wrote: On Jan 10, 2005, at 3:50 AM, Daniel Fagerstrom wrote: Reinhard Poetz wrote: I think of composing an application out of flow calls: function myF() { var newAccount = [here call a flow function of another block] e.g. cocoon.blocks.blockB.createNewAccount(

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

On Jan 10, 2005, at 3:50 AM, Daniel Fagerstrom wrote: Reinhard Poetz wrote: I think of composing an application out of flow calls: function myF() { var newAccount = [here call a flow function of another block] e.g. cocoon.blocks.blockB.createNewAccount(); if(newAccount.t

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Reinhard Poetz wrote: Daniel Fagerstrom wrote: A question here is what flowscript functions that should be exported from a block. I would prefer to explictly enumerate the functions and possibly whole scripts that are exported rather than exporting everything in the map:flow sections. Maybe we

RE: ANN: [portal] New CachingPortletAdapter

> -Original Message- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Friday, January 07, 2005 5:46 PM > To: dev@cocoon.apache.org > Subject: Re: ANN: [portal] New CachingPortletAdapter > > > DURDINA Michal wrote: > > Sorry for just a quick response. > > > > JSR168 - portlet sp

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: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Daniel Fagerstrom wrote: Reinhard Poetz wrote: I think of composing an application out of flow calls: function myF() { var newAccount = [here call a flow function of another block] e.g. cocoon.blocks.blockB.createNewAccount(); if(newAccount.type == "xyz") { cocoon.s

Re: [BUG?] JavaFlow and getComponent

Hmm, ok. But why this exception occurs? Maybe I have done something wrong, but I don't know what. I have compiled the "standard" by just using the build script. After compiling I had copied the webapp folder into my tomcat and then restarted tomcat. Do I have to separately activate the compilin

Re: Blocks, Flow and Dependencies [was RE: Splitting xconf files step 2: the sitemap]

Reinhard Poetz wrote: I think of composing an application out of flow calls: function myF() { var newAccount = [here call a flow function of another block] e.g. cocoon.blocks.blockB.createNewAccount(); if(newAccount.type == "xyz") { cocoon.sendPage("xyz"); } e

Cocoon-2.1.X Tests Failure 01/10/05

Automated Cocoon Unit tests failed! Full log file if this unit test run is available here: http://nagoya.apache.org/~vadim/cocoon-test-log-20050110.log Last messages from the log file: == [foreach] reader-mime-type.xml:39

Re: Inercepted Flowscript (Was: [RT] Pre- and Postfunctions in FlowScript?)

Jens Maukisch wrote: Hi, There is a cocoon block with intercepted flowscript that was supposed to do a functionality similar to what you describe. I am not aware of current state of this block though. Thanks for the info, looks very good. Is anyone using/developing this block? With kind rega