Chris Harris wrote:
> For CMP 2.0 it seems that the Remote becomes much
> more important and the Bean class becomes less so.
I think that's a fair assesment although for the wrong reasons. Because
of container managed relationships. Now, all that stuff you used to do
keeping primary keys of related beans can be thrown away and you let the
container do a lot of the work for you. The bean now becomes just a
declarative thing with a few method implementations if you need them for
validity checking. So really what is happening is you are not changing
the amount of remote interface methods, but reducing the amount of code
cutting in the bean implementation class. Relatively, the remote
interface becomes more important, only because the implementation has
become less so.
As the spec says - EJB 2.0 and EJB 1.1 are not compatible. Use one or
the other. They are completely different mindsets used in the design and
implementation of middleware code.
--
Justin Couch http://www.vlc.com.au/~justin/
Freelance Java Consultant http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
- Greg Bear, Slant
-------------------------------------------------------------------
===========================================================================
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".
