Daniel Bradby wrote:
>
> 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?
If you have no constructor, then by definition you have a public constructor
with no arguments. Java provides it for you.
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
