Hi,
This requirement for EJBs is a carryover of the same requirement for regular
JavaBeans. A argument-less constructor is needed to allow dynamic
instantiation by the server/container. If you don't provide one in your
class, Java provides one for you (sans body).
Gene Chuang
Teach the world... Join Kiko!
<http://www.kiko.com/profile/join.jsp?refcode=TAF-gchuang>
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Bradby
Sent: Wednesday, August 30, 2000 8:56 PM
To: [EMAIL PROTECTED]
Subject: Spec Clarification: constructors in EJBs
I was cleaning up some EJB code and browsing through the bean providers
responsibilities in the EJB spec (as one does) and noticed that the spec
requires a session bean (6.10.2) and an entity bean (9.2.2) to " ....
have a public constructor that takes no parameters."
I noticed the only examples I could find that actually did this was
Sun's, and they only do it in the session beans.
Anyone throw any light on this strange requirement? And why no one
actually does it?
Thanks
---
Daniel Bradby
BJS Australia
[EMAIL PROTECTED]
===========================================================================
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".
