From: Andrzej Jan Taramina
Ugo suggested:
map:match pattern=*/profile/edit
map:call function=dumpData/
/map:match
map:match pattern=view
map:generate src=cocoon://generate/
map:transform src=homePage.xsl/
map:serialize/
/map:match
function
Reinhard Poetz wrote:
I don't like it that we blur the Flowscript concept to achieve things
that can already be done today nearly in the same way some of you
propose. In the long run I fear that nobody knows what the Cocoon
Control flow is about and everybody talks about different things. I
think
On 13 Nov 2003, at 00:20, Andrzej Jan Taramina wrote:
Ugo suggested:
map:match pattern=*/profile/edit
map:call function=dumpData/
/map:match
map:match pattern=view
map:generate src=cocoon://generate/
map:transform src=homePage.xsl/
map:serialize/
/map:match
function
Tim Olson wrote:
map:match action=*/profile/edit
map:call function=dumpUserData/
map:call function=dumpOrderData/
map:call function=dumpNewsItems/
map:generate src=cocoon://generate/
map:transform src=homePage.xsl/
map:serialize/
/map:match
map:match
Tim Olson wrote:
map:match pattern=view
map:generate src=cocoon://generate/
map:transform src=homePage.xsl/
map:serialize/
/map:match
i thought the original intention was to make the flow clearer? now we have
three blocks of code to follow instead of one...
Well, almost, you can reuse
Ugo suggested:
map:match pattern=*/profile/edit
map:call function=dumpData/
/map:match
map:match pattern=view
map:generate src=cocoon://generate/
map:transform src=homePage.xsl/
map:serialize/
/map:match
function dumpData() {
dumpUserData();
Do you want to enforce the fact that flowscript calls (either
function or continuation) *must* redirect using sendPage,
sendPageAndWait or redirectTo and that, should it not be the case, a
ProcessingException be raised?
[ ] no, let the sitemap execution continue after the map:call if
there
On 10.11.2003 21:15, Sylvain Wallez wrote:
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either function
or continuation) *must* redirect using sendPage, sendPageAndWait or
redirectTo and that, should it not be the case, a ProcessingException
I am still learing to vote properly ;-)
Sylvain Wallez wrote:
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either
function
or continuation) *must* redirect using sendPage,
sendPageAndWait or redirectTo and that, should it not be the
Sylvain Wallez wrote:
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either
function or continuation) *must* redirect using sendPage,
sendPageAndWait or redirectTo and that, should it not be the case, a
ProcessingException be raised?
So
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either function
or continuation) *must* redirect using sendPage, sendPageAndWait or
redirectTo and that, should it not be the case, a ProcessingException be
raised?
[ ] no, let the sitemap
Sylvain Wallez wrote:
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either
function or continuation) *must* redirect using sendPage,
sendPageAndWait or redirectTo and that, should it not be the case, a
ProcessingException be raised?
[ ] no,
Sylvain Wallez wrote:
Do you want to enforce the fact that flowscript calls (either function
or continuation) *must* redirect using sendPage, sendPageAndWait or
redirectTo and that, should it not be the case, a ProcessingException be
raised?
[ ] no, let the sitemap execution continue after
Sylvain Wallez wrote:
Let's reformulate this into a proper vote.
Do you want to enforce the fact that flowscript calls (either function
or continuation) *must* redirect using sendPage, sendPageAndWait or
redirectTo
Unico added: or sendStatus!
and that, should it not be the case, a
14 matches
Mail list logo
