Hello folks,
I have a "philosophical" question that relates to web apps:
Suppose for the sake of this example that the smallest component of a
web app is an XSP page and that I want to do something like this:
<xsp:logic>
if (test==true) {
<foo>bar</foo>
}
else {
<bar>foo</bar>
}
</xsp:logic>
I call this internal flow control, because it occurs within a component.
In contrast to that, external flow control would be between components,
such as HTTP redirects from one XSP page to another or HTML forms that
make a POST request to another XSP page.
As far as I understand, for external flow control there are some things
out there, namely a forms processing framework that uses the Action
framework and Schecoon.
However, what are my options for internal flow control? Here are some
answers that come to my mind:
1) Use the implementation language (here: Java) for flow control like it
is shown in the example above.
2) Write a logic taglib that wraps the Java code in order to make it
independent from the implementation language.
3) Invent a Sitemap-like central repository, where individual components
or groups of components are selected and their internal flow control is
specified.
4) Avoid internal flow control altogether. If a component needs internal
flow control, this is a sure sign that it should be split up into
several smaller components and external flow control should be used
between them.
To me none of these answers are really satisfactory. Is there a
"Cocoon-way" for internal flow control or is it stipulated that Cocoon
should leave this to the individual preferences of the user?
Thank you very much in advance for any comments,
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
