cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piroumian Konstantin <KPiroum...@protek.com>
Subject RE: continuation fear (was Re: [status & RT] design challenges)
Date Fri, 12 Apr 2002 14:16:39 GMT
> From: Ivelin Ivanov [mailto:ivelin@apache.org] 
> From: "Piroumian Konstantin" <KPiroumian@protek.com>
> 
> > >That's too much of a price to pay when an interpreted
> > > language already does it for me.
> >
> > The key phrase is "does it for me" - interpreted language is another
> > language that you should learn, you should get used to it 
> and you should
> > study also a lot of "best practices" samples and good docs 
> to learn from.
> 
> Second that.
> I am starting to understand why Schecoon is a lot more 
> flexible and powerful
> than I originally thought.
> However I would ask Ovidiu to consider at least an 
> alternative "poor man"
> solution which will do the job for many of us. I will not 
> repeat myself more
> than just refering back to the <map:fetch> construct as an 
> extension to
> <map:redirect> and <map:call> (or <map:forward> :).
> 
> Konstantin is <map:fetch/> extension getting anywhere close 
> to your flow map
> solution?

My solution does not require any additions to sitemap. It can be implemented
using actions. But in some cases you'll need to use a selector to choose the
according view (just like the <forward /> in struts-config).

Btw, Ovidiu, if understand the interpreted approach correctly, you can
forward controll to a different pipeline in sitemap than the calling one
using sendPage("another_pipeline"). Is that right? So, you don't need a
selector after your <map:call />? If yes, then it's much better then using
actions with selectors.

Regards,
  Konstantin

> 
> 
> Thanks,
> 
> Ivelin
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message