The remote interface of an enterprise bean is definitely
not a Java Bean, because Java Beans must have a default
constructor.
While the implementation of an enterprise bean can
fulfil all requirements to count as a Java Bean,
this is quite worthless because implementations
will only be instantiated by the EJB server.
Don't try to think of an enterprise bean "along the
lines of Java Beans"; that will lead to confusion,
because they are totally different beasts.
Wolf
===========================================================================
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".
