I guess it be a new case.
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 iter
Vic, the separation of view and model is clear on your
approach, liked it.
However, there`s still one of the coupling i
mentioned.
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
See if this methodology helps you separate the 2.
When I start a project I do not care about DB or model; I only care
what the client wants, like what fields, where, etc.
I work w/ them to create html mock ups as requirments.
Is this what they want?
Once that's done, it's easy.
I rename HTML
3 matches
Mail list logo
