Quoting Piroumian Konstantin <[EMAIL PROTECTED]>:

> > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] 
> > Quoting Jeff Turner <[EMAIL PROTECTED]>:
> > 
> > > Ehm.. more code, less talk :)
> > 
> > Before you guys start coding something that looks like FS 
> > from 10 Km, please, 
> > make a formal votation by writing a small description of what 
> > you are trying to 
> > do. TIA
> 
> After learing what is the FS, I should say, that input modules are really
> good replacements for most of the actions and it's not FS, but a better
> approach for obtaining values to be used in sitemap attributes. When all the
> request, session input modules are implemented, we can deprecate all the
> actions that read a value (e.g. RequestParamAction, DOMReaderAction, etc.).
> Actions would be needed for setting values, though, but this can be easily
> done in the flow layer.
> 
> IMO, Input modules make sitemaps look shorter and more elegant. 
> Compare:
> 
> <!-- action version -->
>   <map:act type="request-param">
>     <map:generate src="..." />
>    <map:transform src="{stylesheet}.xsl" /> <!-- We get the stylesheet name
> from a request parameter -->
>   </map:act>
> 
> <!-- input module version -->
>     <map:generate src="..." />
>    <map:transform src="{request-param:stylesheet}.xsl" /> <!-- We get the
> stylesheet name from a request parameter -->

nononono you got me wrong here: FS was referred at using the complexity of 
XPath to obtain values from the environment. It works, but it might create too 
many contracts.

Talking about input-modules vs. actions, I can't agree more: I *don't* like 
actions and I try not to use them *ever*! I hate them! expecially the stupid 
jump-me-if-I-return-null markup which is not self-describing and it's a pain to 
maintain if you have nested actions.

But I totally agree: flow + input-modules make actions useless.

Just don't make input-modules too hard to use, ok?

-- 
Stefano Mazzocchi                       <[EMAIL PROTECTED]>
------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to