I don't know that we can generalize here and say "IBM is in favor of fine
grained entity beans...". This is sort of an educational piece. A kind of
"Intro to EB's 101" if you will. This doesn't imply that it is universally
accepted "best practice" at IBM that things be done this way. Unfortunately
a thousand newbie Java folks will take this code and build systems based on
it that have terrible performance and don't scale. Or fortunately if your
the vendor that comes in for the "second surgery" (also known as ambulance
chasing). Here we go again (made a nice living doing this in the Smalltalk
world, thank you very much)...
Like most EB/CMP first implementations, it would appear VisualAge has also
taken the simplistic approach that EB=row. So the tooling isn't where it
needs to be yet. I doubt IBM is sleeping either...
-Chris.
> -----Original Message-----
> From: Chip Wilson [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, September 03, 1999 8:29 AM
> To: [EMAIL PROTECTED]
> Subject: IBM comes out in favor of fine-grained entity beans
>
> IBM posted a technical artical on the VisualAge Developer's Domain that
> recommends using entity beans for fine-grained, dependant objects.
> Examples from the article include the address and job history for a
> resume.
>
> http://www.software.ibm.com/ad/r/99enews12/vajejb/
>
> Comments?
>
> --Chip
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
