Back to the main problem...
I found some interesting links about the Composite View; it was a good suggestion to look after that!
Core J2EE Patterns - Composite View
Blueprints - Composite View
They talk about a template (represents a complex page layout) which include subsections like banner, footer, some boxes …
So every subsection is a atomic part of a complex page. My first question was from where do I get the data for such subsections? My supposition was, the one “Command” collects all the data and passed it with a single DTO Object to the view, not very nice, because the DTO gets huge and complex, but a good separation of content and design?! (Only a push concept, nothing to pull!)
<tr align="left" valign="middle">
<td width="70%" align="center">
The Kyber approach?!:
If I understand you right kyber, you said the data is assembled by subactions, so every subaction matches one subsection?!
The Proton approach?!:
If I understand you right … ;-) One “main action” for e.g. “UserEdit” with a template which includes subsections. The main action gathers the data (only for which belongs to the “UserEdit”!) and passed it to the view (A push concept). The view uses a complex template which consists of subsections. Each subsections pull the data from Viewhelpers (?!). In that case the View collects data! So Captain Protons approach is a combination of a push and pull concept?!
Core J2EE Patterns - View Helper
To my opinion the Proton approach is not so complex like the kyber approach. I would prefer Protons suggestion.
My question now, what do you think about my theories? Have I misunderstood everything or I am right?
Perhaps we could create some easy to understand sample code for the Proton approach? :-)
Greetings from Germany