cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <>
Subject Re: Looking for data persistance method recommendation
Date Thu, 22 Jan 2004 03:37:34 GMT
mirko dijo:
> Antonio Gallardo wrote:
>  > ...
>> I think it is a good idea to have 2 classes from the SoC point of view.
>> The employee.class are the data (a bean). The employeeImpl.class is the
>> model in the MVC paradigm.
>  > ...
> Sorry but I thougt model=data in MVC. Then separating it is just strange
> for me. You have situations where you have two objects that represents
> the same domain object.

I don't see it as you suggested. For me, Model= businnes logic. Businnes
logic involves manipulation of data (a bean) and the bean are data that
fly between Controller (Flow) and View (Woody).

In our case we prefer to have all the model written in Java and the
Controller just make calls to the model.

The model is separated in 2 types of classes: Beans and Handlers. The flow
interact directly to handlers.

Best Regards,

Antonio Gallardo.

> In my opinion from SoC point of view the flowscript developer should use
> only one type of domain objects (pass it to view, bind it to woody,
> etc), and let the "data developer" decide if it is mapped to OJB or
> plain JDBC code.
> Reagrds,
> mirko
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message