It should be easier if you think in Cocoon as framework that implements
the "pyramid model of web contracts" as stated in Cocoon developer's
Handbook by Lazlo Moczar and also on
http://cocoon.apache.org/2.1/introduction.html
The idea of confining cocoon with a 3/4-tier architecture is probably not
very accurate since the idea behind the MVC model is to break the chains
of the n-tier architectures. The more tiers you add, the more difficult it
will be to precisely define what is the role of each tier.
Check this article :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/crystlmn/HTML/crconreportdeploymentscenarios.asp
for an idea about a 3 tier application based on crystal reports. Based on
this i would say that
http://cocoondev.org/xreporter/docs.html
is a 3- tier application.
Greets,
CarlosN.
On Wed, 14 Sep 2005, Johannes Becker wrote:
Hi,
Thanks again for the answers and opinions.
I guess it depends on how you define the presentation layer
That's the point of confusion. What I learned at university, and this mustn't
be right of course:
Presentation layer consists of
a) the presentation
b) dialog control
So my opinion is that the flow and sitemap control the dialog, because they
are deceiding which page to display. Or am I missunderstanding "dialog
control"?
I guess it depends on how you define the presentation layer. In my opinion
the sitemap itself doesn't create the
presentation/view, it defines/*controls* which components (generators,
transformers,serializers, readers) are
used to build the view.
And this makes even more sense to me.
Boy, I'm confused now.
Here the link concerning the service layer:
http://agylen.com/wp-content/Ugo_Cei_ApacheCon_2005EU.pdf
Thanks
Jonny
Jason Johnston wrote:
Hi,
thanks for the answers.
add in JXTemplates and XSLT
Thanks for the hint. I'll add them
So what I understood is, that Flow is present in both layers: Presentation
and Control Layer?
I'm not sure how you'd consider Flow being presentation. It seems pretty
clearly in the control layer... it's even named "Control Flow" in the
docs.
Is the Sitemap also both (since it has a navigating-function in the
presentation layer)? My answer would be yes.
I guess it depends on how you define the presentation layer. In my
opinion the sitemap itself doesn't create the presentation/view, it
defines/*controls* which components (generators, transformers,
serializers, readers) are used to build the view.
It's difficult to define a system like Cocoon in these terms, as each
layer often has its own n-tiers within. For instance, CForms would
probably go in the Presentation bucket in your list, but within CForms
there are sub-tiers (form model, bindings, templates, flow).
To push my other question:
Ugo wrote in his presentation at the ApacheCon about a service layer.
Which layer (from the ones above) does this match?
I'm not familiar with this presentation; can you post a link or quote the
relevant portions here?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
