Cedric,
>
> Agreed. Not only is 100 domain objects a common case for any medium-size
> projects (it can be a lot more than that), but we're seeing more and more
> applications that have
well, the data model is represented by about 100 CMP entity beans. domain
objects are a lot more but not all of them are persistent.
-snip
>
>
> Brace yourselves, we're going hyperbolic. Sooner than you think.
>
I'm not sure I understand your position in this. Are you saying that code
generation should not be necessary to make up for poor design or do you agree
with the approach of using code generation as a valid tool for getting rid of
some parts of the maintenance burden?
I strongly believe that you need a combination of both handcoded parts and
parts that can be tackled by tools generating code from meta information
which saves you a lot of headaches in QA and maintenance. Finding the right
balance is what makes a good software architect and no tool is going to make
that decision for you, no matter how good because it is a trade-off in each
individual case.
do you see the problem with relationships and deployment units I described or
am I missing something important in my assessment in your opinion?
Regards,
Robert
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
