Flowmaps/Logic

[Michael Mangeng <mi...@ideefix.net>]

Hi all!

I don´t have very much expirience with c2 and maybe the following question
is silly and i´ve missed something... sorry if it is so...

I´ve followed the flowmap discussion and i think the basic idea is
_very_very_ nice...

BUT - as far as i understand this - the flowmaps are here to describe the
flow, or to use another word - the sequence of pages the user is beeing
served (with notice to validation, errors and so on)... but where do we put
general logic...

For example i have a internal/* area and i want to do a simple 'check if the
session attribute 'user' is set to something != null)... on each request...
i think this is possible in the flowmap... and it _could_ be there.. but i
think a

<map:match pattern="internal/*">
    <map:act type="sesauth">
       <map:continue with="{1}"/>
    </map_act>
    <map:redirect-to uri="login"/>
</map:match>

is much nicer.. after all.. you would have to implement user auth on each
flowmap... -and on pages where the flowmap does not have a effect on...

next point:
i want to do a 'more-complex' calculation based on the request...
this a.) is no 'flow-specific-logic'  in my sight and b.) it would be much
more complicate to implement such things in a flowmap with e.g. javascript..
(than with pure java in a action)

so my overall question:
---------------------------------
imagine that actions are deprecated, is there a way to do the points
mentioned above at another position than the page, for example xsp, itself
or the flowmap  ?


thanx, greetings
mike
---------------------------------------------
Nothing has value but that which you grant it.
----------------------------------------------


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

Re: Flowmaps/Logic

[Stefano Mazzocchi <st...@apache.org>]

Michael Mangeng wrote:
> 
> Hi all!
> 
> I don´t have very much expirience with c2 and maybe the following question
> is silly and i´ve missed something... sorry if it is so...
> 
> I´ve followed the flowmap discussion and i think the basic idea is
> _very_very_ nice...
> 
> BUT - as far as i understand this - the flowmaps are here to describe the
> flow, or to use another word - the sequence of pages the user is beeing
> served (with notice to validation, errors and so on)... but where do we put
> general logic...
> 
> For example i have a internal/* area and i want to do a simple 'check if the
> session attribute 'user' is set to something != null)... on each request...
> i think this is possible in the flowmap... and it _could_ be there.. but i
> think a
> 
> <map:match pattern="internal/*">
>     <map:act type="sesauth">
>        <map:continue with="{1}"/>
>     </map_act>
>     <map:redirect-to uri="login"/>
> </map:match>
> 
> is much nicer.. after all.. you would have to implement user auth on each
> flowmap... -and on pages where the flowmap does not have a effect on...
> 
> next point:
> i want to do a 'more-complex' calculation based on the request...
> this a.) is no 'flow-specific-logic'  in my sight and b.) it would be much
> more complicate to implement such things in a flowmap with e.g. javascript..
> (than with pure java in a action)
> 
> so my overall question:
> ---------------------------------
> imagine that actions are deprecated, is there a way to do the points
> mentioned above at another position than the page, for example xsp, itself
> or the flowmap  ?

Ok, let me state this clearly so that everybody is assured:

    Flowmaps and Actions will cohexist until we decide the opposite.

For now, I'm *NOT* proposing to deprecate them at all, so fear not.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



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