Class.newInstance() does call the default constructor. However, I would put
in object creation in ejbCreate(). constructor should be empty.
-- Bill
> -----Original Message-----
> From: Chris Raber [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 24, 2000 1:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Creation of objects in stateful EJB
>
>
> Don't use the constructor in EJB. The container doesn't call
> it (it uses
> Class.newInstance()).
>
> Put your intialization in ejbCreate()
>
> -Chris.
>
> > -----Original Message-----
> > From: Roger Kjensrud [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 24, 2000 12:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: Creation of objects in stateful EJB
> >
> > I have a stateful session bean that uses a couple of java objects. I
> > wonder
> > where is the best place to create these, in ejbCreate() or in the
> > constructor? Is there a difference?
> >
> > Any thoughts are appreciated,
> >
> > Roger Kjensrud
> >
> >
> ==============================================================
> ============
> > =
> > 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".
>
===========================================================================
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".