<flame-bait>
Supposedly, the beans provided by third parties will not mutate over the
development.
The fragility comes from rapidly evolving components. It's as fragile as
binary compatibility is.
IMHO, this approach prevents closing versions of the components and reusing
them in their
binary form. It's a quick way to turn Java into C flat ;-).
It harms the ability to connect to pre-built components, which would be done
by code instead of by the container's CMR abilities.
I'm wondering exactly how each developer will hack his/her way around this.
Most likely, opening the pre-built component jar, extracting class files and
part of the deployment descriptor, then adding all of it into the final
application's jar (some copy/paste work on the descriptors too).
Truly, this won't kill anybody, but will add up on the con column of
building and selling J2EE components.
Then there would be less invesment on R&D. Then there good be less
components. Then the quality of those components would be low and remain
low.
</flame-bait>
Or maybe MrMagic and I are just martians. ;-)
JP
PS: Anybody that doesn't agree I am a martian please tell me so at
[EMAIL PROTECTED] TIA.
> -----Original Message-----
> From: Cedric Beust [mailto:[EMAIL PROTECTED]]
> Sent: Miércoles, 26 de Septiembre de 2001 11:54
> To: [EMAIL PROTECTED]
> Subject: Re: EJB 2.0 final - what we have to live with now
>
>
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of MrMagic
>
> [remote relationships]
>
> > Where is it fragile? Where is it not flexible? Do you know Apple's
> > EOF?
>
> It's fragile in the sense that when you modify one end of the
> relationship, you
> need to remember in what jar (or worse, jars) the other ends
> live and modify all
> of them.
>
> Customers have typically dozens (if not hundreds) of jars,
> each of them
> containing several EJB's.
>
> Fragile enough? :-)
>
> --
> 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".
>
>
> ______________________________________________________________
> ______________
> For your protection, this e-mail message has been scanned for Viruses.
> Visit us at http://www.neoris.com/
>
==========================================================================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".
