just use the session beans as a facade to the entity beans, as in don't give
client access to the entity beans they must all go through your session
bean. This a better design approach anyway as your entity beans can remain
reusable
-----Original Message-----
From: Dave Ford [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 15, 2000 3:46 PM
To: [EMAIL PROTECTED]
Subject: Omit Home Interface?
Is it allowed to create an ejb and NOT provide a home interface? For
example, I have a session ejb called Schedule and an entity ejb called
Appointment. I would prefer to have Schedule be the factory for creating and
finding appointments instead of creating a separate AppointmentHome
interface. This seems like an extra, unnecessary step.
Thanks,
Dave
===========================================================================
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".
