cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <pati_giac...@yahoo.com>
Subject RE: [C2]Action proposal (long)
Date Fri, 10 Nov 2000 13:29:01 GMT

--- Brian Olsen <bro@sanderman.com> wrote:
> 
> > I'd like to thank you all for patiently waiting for this proposal.
> > I know I was very ternse the last days. This is because I'm have 
> > to finish some projects apart from Cocoon.
> 
> It wasn't such a long waiting. :-) But I'm also new to this list.
> 

<snipped already known information/> 
> > 
> > Question: Is it suitable to implement some semantic directly into 
> > the sitemap to select the right action out of an action-chain 
> > because usually only one action gets posted by a client and 
> > executed out of a set of explicit actions? Example:
> > 
> > 	<action-chain name="database-manipulation>
> > 	 <act type="insert-action" action="insert"/>
> > 	 <act type="delete-action" action="delete"/>
> > 	 ...
> > 	</action-chain>
> > 
> > The posted action is selected according to the action attribute and
> 
> > by a TBD mechanism for the sitemap to aquire the posted action.
> 
> -1 This sematic is dbl. implementing things that is really a
> selector.
> In it's essence the above is just a short for the action/selector
> sematic.
> You still need some "Action" or "ActionChainParser" to extract the
> data to
> be able to select the correct action.
> I like the idea of an action chain for a stack of events but as an
> action
> selector I simply don't see the need.
> In your own example you demonstrate a case where the power of using a
> selector instead of making an action chain selctor is shown. When you
> don't
> JUST want an action but also a special generator or transformation
> applied.

Yes, I can't agree more. The proposed example above (action-chain with
action attribute) only reduces verbosity but adds redundant semantics.
So one question raises. What are the legal elements in a action-chain? 

> >   <action-chain name="secure-data-entry">
> >    <act type="session-validator"/>
> >    <act type="admin-authorizer"/>
> >    <act type="validate-form">
> >     <parameter name="schema" 
> >       value="my-path-to-schema-resource.xsd"/>
> >    </act>
> >    <act type="save-form"/>
> >   </action-chain>
> 
> It is not just the action that generate state information. The chain
> itself
> should also generate some information in case one of the actions in
> the
> chain fail.
> When the authorization fail I want the make one response if the form
> didn't
> validate I want another one.

Can you suggest a way to achieve this?

Giacom

=====
--
PWR GmbH, Organisation & Entwicklung      Tel:   +41 (0)1 856 2202
Giacomo Pati, CTO/CEO                     Fax:   +41 (0)1 856 2201
Hintereichenstrasse 7                     Mailto:Giacomo.Pati@pwr.ch
CH-8166 Niederweningen                    Web:   http://www.pwr.ch

__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one Place.
http://shopping.yahoo.com/

Mime
View raw message