cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: [RT] Attribute Rendering and CForms Convertors
Date Sun, 07 Nov 2004 21:00:52 GMT
On 07.11.2004 18:23, Ralph Goers wrote:

>> For web applications:
>> - the model is the first to be agreed upon/designed/implemented
>> - the model is the core of the application and most weight is shifted 
>> in that direction
>> - the model is strongly typed, has a lot of constraints. Almost whole 
>> model consists of POJOS.
>> - the model does not change much. If it does it's much bigger problem 
>> than just updating the views because it involves a lot of business 
>> logic to be changed.
> 
> Maybe this is just a different way to say the same thing.  In our 
> environment we designed and developed the business entities first 
> independent of any view.  We then determined what DTOs needed to be 
> transfered to the presentation tier based upon the data the use cases 
> would need, sharing DTOs where that is possible.  Then the Business 
> Delegates/Session Facades were implemented to return those DTOs.  At the 
> same time the View was implemented using mock DTOs. Finally the two 
> tiers were tied together.

That's the way we did it until now too. But all with only one view. 
What's your experience when supporting your multiple views? An 
additional needed field in one of your forms should result in editing so 
many views or isn't it?

Joerg


Mime
View raw message