If there are 2 logical forms like master (name) and detail(list of transactions, that means the 1 form bean has to mirror it so you would have to nest a bean.
(and... once the client approves... I would write a DAO).
As far as MDA.... I myself use requirments based iterative development. (and therefore I do not model untill the both the mock and the prototype are validated. Then I model).
But... any kind of matianance grays the area.
I kind of disagreee with people that do UML or MDA BEFORE they validate what the client wants.
.V
Leandro Melo wrote:
Suppose that one year later your client decided to
change the information contained in one of the pages.
He now wants the all the stuff from 2 pages in only 1
page. You`d probably have to make some changes in your
action. As you said, you created form beans based on
the html fields. Naturally, the way that the actions
manipulate these form beans will change (maybe just a
little if well disigned). THis is the other coupling i`m talking about.
I`m not saying this is wrong or this is bad modelling,
whatever. I`m just asking if there`s a very abstract
model where we don`t have the coupling. Maybe i`m
looking a little for mda...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
