> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Kr�ger

> > I would say that any data model that has 100 domain objects with no
> > independent subsets is going to be a development and maintenance nightmare
> > no matter how it's deployed. We have a similar number of domain objects but
>
> have to disagree here since we cope very well with code generation and a good
> build system based on ant always having keeping everything in sync (db-model,
> EJBs, deployment descriptors and lots more of related code) and the
> deployment organization also works without any tedious side effects.

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

- hundreds of EJB's
- classes with hundreds of methods, each of this method maxed out in size (64k
in bytecode I think... <sigh>)

Before you dismiss these numbers as either not realistic (what developer would
come up with something like this?) or "a nightmare to maintain", keep in mind
that a lot of the code we write by hand today will be generated by tools
tomorrow.

We've seen that happen in the past.  Assembly language, then C generating
assembly, then C++ generating C, then compilers generating C++, and then
meta-tools generating code in 4GL languages.  The next step is obvious, isn't
it?

Not only will EJB's be generated by tools very soon, but whole J2EE applications
will be written and maintained like that.  And this will soon be considered
"low-level".  Nobody will want to hand-code any part of this, just like Java
developers would probably cringe if they had to write Assembly language like
they did twenty years ago.

Brace yourselves, we're going hyperbolic.  Sooner than you think.

--
Cedric

===========================================================================
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".

Reply via email to