You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Piroumian, Konstantin" <KP...@flagship.ru> on 2001/05/28 11:46:02 UTC
[C2] Suggestion for FlowMap
Hi, Cocooners!
How do you feel about having a possibility to inherit action sets and extend
them by other actions. In this case you can have one root action-set for the
whole web application, which can include: session tracking, language
selection, authorization, etc. actions. Then in every particular case the
sub-system can add its own behavior by extending that actions set. E.g.:
<action-set name="main">
<act type="check-session" />
<act type="lang-select" />
<act type="some-other-action" />
</action-set>
Then it can be extended:
<action-set name="forms" extends="main">
<act type="form-validate" />
<act type="navigate" />
</action-set>
<action-set name="menu" extends="main">
<act type="menu-action" />
</action-set>
Something like that.
Maybe this can be used if a Flow Map concept will be implemented in C2.
Regards,
Konstantin Piroumian.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by "Piroumian, Konstantin" <KP...@flagship.ru>.
>
> IIRC this is already addressed by:
>
> <action-set name="forms">
> <act set="main"/>
> <act type="form-validate" />
> <act type="navigate" />
> </action-set>
>
> This way you can controll the point where a super-set takes place as well.
>
> Giacomo
Thank you. I didn't know that such syntax is allowed.
Konstantin.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Sylvain Wallez <sy...@anyware-tech.com>:
>
>
> giacomo a écrit :
> >
> > On Mon, 28 May 2001, Sylvain Wallez wrote:
> >
> > >
> > >
> > > Giacomo Pati a écrit :
> > > >
> > > > Quoting "Piroumian, Konstantin" <KP...@flagship.ru>:
> > > >
> > > > > Hi, Cocooners!
> > > > >
> > > > > How do you feel about having a possibility to inherit action
> sets and
> > > > > extend
> > > > > them by other actions. In this case you can have one root
> action-set for
> > > > > the
> > > > > whole web application, which can include: session tracking,
> language
> > > > > selection, authorization, etc. actions. Then in every particular
> case
> > > > > the
> > > > > sub-system can add its own behavior by extending that actions
> set. E.g.:
> > > > >
> > > > > <action-set name="main">
> > > > > <act type="check-session" />
> > > > > <act type="lang-select" />
> > > > > <act type="some-other-action" />
> > > > > </action-set>
> > > > >
> > > > > Then it can be extended:
> > > > >
> > > > > <action-set name="forms" extends="main">
> > > > > <act type="form-validate" />
> > > > > <act type="navigate" />
> > > > > </action-set>
> > > > >
> > > > > <action-set name="menu" extends="main">
> > > > > <act type="menu-action" />
> > > > > </action-set>
> > > >
> > > > IIRC this is already addressed by:
> > > >
> > > > <action-set name="forms">
> > > > <act set="main"/>
> > > > <act type="form-validate" />
> > > > <act type="navigate" />
> > > > </action-set>
> > > >
> > > > This way you can controll the point where a super-set takes place
> as well.
> > > >
> > > > Giacomo
> > > >
> > > Going further on Konstantin's question : is it possible to define
> > > sitemap logicsheets that could be used to augment the sitemap syntax
> > > with higher level concerns, such as the ones proposed in the above
> > > action-sets ?
> > >
> > > There's some code in SitemapMarkupLanguage to handle
> <?xml-logicsheet?>
> > > PIs and <map:logicsheet> tags, but I've never used them. Does
> someone
> > > have some experience with this ?
> >
> > Why don't you shut your mouth :)
> >
> Sorry, but you know I like asking questions ;)
>
> > No, seriously. Yes, it is possible to use those PIs etc. because the
> > underlaying engine is the same markup-to-code as the XSP stuff uses.
> But
> > never ever ask any question about that if you'll use it and have any
> > problems with it.
> >
> > Giacomo
> >
> Mmh... Does this mean "it's not tested so who uses it debugs it" or
> "sitemap logicsheets are a bad thing" ?
Both ;) I can't stop people how are aware of it to use it but I can propose not
to use it because it was not meant to do nor is it tested.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
giacomo a écrit :
>
> On Mon, 28 May 2001, Sylvain Wallez wrote:
>
> >
> >
> > Giacomo Pati a écrit :
> > >
> > > Quoting "Piroumian, Konstantin" <KP...@flagship.ru>:
> > >
> > > > Hi, Cocooners!
> > > >
> > > > How do you feel about having a possibility to inherit action sets and
> > > > extend
> > > > them by other actions. In this case you can have one root action-set for
> > > > the
> > > > whole web application, which can include: session tracking, language
> > > > selection, authorization, etc. actions. Then in every particular case
> > > > the
> > > > sub-system can add its own behavior by extending that actions set. E.g.:
> > > >
> > > > <action-set name="main">
> > > > <act type="check-session" />
> > > > <act type="lang-select" />
> > > > <act type="some-other-action" />
> > > > </action-set>
> > > >
> > > > Then it can be extended:
> > > >
> > > > <action-set name="forms" extends="main">
> > > > <act type="form-validate" />
> > > > <act type="navigate" />
> > > > </action-set>
> > > >
> > > > <action-set name="menu" extends="main">
> > > > <act type="menu-action" />
> > > > </action-set>
> > >
> > > IIRC this is already addressed by:
> > >
> > > <action-set name="forms">
> > > <act set="main"/>
> > > <act type="form-validate" />
> > > <act type="navigate" />
> > > </action-set>
> > >
> > > This way you can controll the point where a super-set takes place as well.
> > >
> > > Giacomo
> > >
> > Going further on Konstantin's question : is it possible to define
> > sitemap logicsheets that could be used to augment the sitemap syntax
> > with higher level concerns, such as the ones proposed in the above
> > action-sets ?
> >
> > There's some code in SitemapMarkupLanguage to handle <?xml-logicsheet?>
> > PIs and <map:logicsheet> tags, but I've never used them. Does someone
> > have some experience with this ?
>
> Why don't you shut your mouth :)
>
Sorry, but you know I like asking questions ;)
> No, seriously. Yes, it is possible to use those PIs etc. because the
> underlaying engine is the same markup-to-code as the XSP stuff uses. But
> never ever ask any question about that if you'll use it and have any
> problems with it.
>
> Giacomo
>
Mmh... Does this mean "it's not tested so who uses it debugs it" or
"sitemap logicsheets are a bad thing" ?
--
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by giacomo <gi...@apache.org>.
On Mon, 28 May 2001, Sylvain Wallez wrote:
>
>
> Giacomo Pati a �crit :
> >
> > Quoting "Piroumian, Konstantin" <KP...@flagship.ru>:
> >
> > > Hi, Cocooners!
> > >
> > > How do you feel about having a possibility to inherit action sets and
> > > extend
> > > them by other actions. In this case you can have one root action-set for
> > > the
> > > whole web application, which can include: session tracking, language
> > > selection, authorization, etc. actions. Then in every particular case
> > > the
> > > sub-system can add its own behavior by extending that actions set. E.g.:
> > >
> > > <action-set name="main">
> > > <act type="check-session" />
> > > <act type="lang-select" />
> > > <act type="some-other-action" />
> > > </action-set>
> > >
> > > Then it can be extended:
> > >
> > > <action-set name="forms" extends="main">
> > > <act type="form-validate" />
> > > <act type="navigate" />
> > > </action-set>
> > >
> > > <action-set name="menu" extends="main">
> > > <act type="menu-action" />
> > > </action-set>
> >
> > IIRC this is already addressed by:
> >
> > <action-set name="forms">
> > <act set="main"/>
> > <act type="form-validate" />
> > <act type="navigate" />
> > </action-set>
> >
> > This way you can controll the point where a super-set takes place as well.
> >
> > Giacomo
> >
> Going further on Konstantin's question : is it possible to define
> sitemap logicsheets that could be used to augment the sitemap syntax
> with higher level concerns, such as the ones proposed in the above
> action-sets ?
>
> There's some code in SitemapMarkupLanguage to handle <?xml-logicsheet?>
> PIs and <map:logicsheet> tags, but I've never used them. Does someone
> have some experience with this ?
Why don't you shut your mouth :)
No, seriously. Yes, it is possible to use those PIs etc. because the
underlaying engine is the same markup-to-code as the XSP stuff uses. But
never ever ask any question about that if you'll use it and have any
problems with it.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Giacomo Pati a écrit :
>
> Quoting "Piroumian, Konstantin" <KP...@flagship.ru>:
>
> > Hi, Cocooners!
> >
> > How do you feel about having a possibility to inherit action sets and
> > extend
> > them by other actions. In this case you can have one root action-set for
> > the
> > whole web application, which can include: session tracking, language
> > selection, authorization, etc. actions. Then in every particular case
> > the
> > sub-system can add its own behavior by extending that actions set. E.g.:
> >
> > <action-set name="main">
> > <act type="check-session" />
> > <act type="lang-select" />
> > <act type="some-other-action" />
> > </action-set>
> >
> > Then it can be extended:
> >
> > <action-set name="forms" extends="main">
> > <act type="form-validate" />
> > <act type="navigate" />
> > </action-set>
> >
> > <action-set name="menu" extends="main">
> > <act type="menu-action" />
> > </action-set>
>
> IIRC this is already addressed by:
>
> <action-set name="forms">
> <act set="main"/>
> <act type="form-validate" />
> <act type="navigate" />
> </action-set>
>
> This way you can controll the point where a super-set takes place as well.
>
> Giacomo
>
Going further on Konstantin's question : is it possible to define
sitemap logicsheets that could be used to augment the sitemap syntax
with higher level concerns, such as the ones proposed in the above
action-sets ?
There's some code in SitemapMarkupLanguage to handle <?xml-logicsheet?>
PIs and <map:logicsheet> tags, but I've never used them. Does someone
have some experience with this ?
--
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2] Suggestion for FlowMap
Posted by Giacomo Pati <gi...@apache.org>.
Quoting "Piroumian, Konstantin" <KP...@flagship.ru>:
> Hi, Cocooners!
>
> How do you feel about having a possibility to inherit action sets and
> extend
> them by other actions. In this case you can have one root action-set for
> the
> whole web application, which can include: session tracking, language
> selection, authorization, etc. actions. Then in every particular case
> the
> sub-system can add its own behavior by extending that actions set. E.g.:
>
> <action-set name="main">
> <act type="check-session" />
> <act type="lang-select" />
> <act type="some-other-action" />
> </action-set>
>
> Then it can be extended:
>
> <action-set name="forms" extends="main">
> <act type="form-validate" />
> <act type="navigate" />
> </action-set>
>
> <action-set name="menu" extends="main">
> <act type="menu-action" />
> </action-set>
IIRC this is already addressed by:
<action-set name="forms">
<act set="main"/>
<act type="form-validate" />
<act type="navigate" />
</action-set>
This way you can controll the point where a super-set takes place as well.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org