Robert Krüger wrote:
>
> Hi all,
>
> I just read the revision history of 2.0 final and if it is complete I have to
> say that as a system architect I am very disappointed that none of the very
> valid points made on this forum about 2.0 CMP problems have been addressed.
> Looking at applications we have currently deployed on 1.1 CMP I can say that
> 2.0 CMP is in some aspects a step back and in others it doesn't achieve what
> it was meant to be (as I understood it):
> - data model partitioning cannot be reflected in ejb deployment due to
> restricting relationships to one ejb-jar (currently an application we are
> working on has about 100 entity beans being clustered in 14 ejb-jars, which
> would have to move into one ejb-jar if ported to 2.0 CMP - a development and
> maintenance nightmare)
How many existing object relational mapping tools allow a developer to
incrementally deploy and evolve a complex object schema while providing
fully managed relationships that support full navigation and referencial
integrity?
This was a problem that OODBs had great difficulty solving (some would
argue that it was never fully solved). OR tools have never, to my
knowledge, solved it. They always require that an object schema be
evolved as a whole and deployed as a whole.
If CMP were to have required that EJB containers provide unbounded
incremental deployment of a single object schema what technology would
they have used to meet this requirement? How much would you be willing
to pay for such a groundbreaking solution? How long would you be willing
to wait for it?
EJB CMP is simply a standard API for a container provided object
relational mapping tool. It benefits from the fact that the container
can optimize its integration with the EJB lifecycle; however, CMPs
design was specifically restricted to allow it to be implemented with
existing OR technologies.
As others on this thread have noted, large apps need to be architected
as loosely coupled modules. By definition, these modules can't be
implemented with a single intertwined object schema.
-- Mark
==========================================================================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".
