Hi Dave,
The home of a staless bean - any bean - act as a factory to create objects
of that bean type on which business methods are invoked.
An application can have any number of stateless bean, each having its own
home (factory). The home has to be separate for each type of Stateless
session bean (eg FooSLBean, RooSLBean). You dont want to create FooObject
from RooHome !!
If the spec were to say that there can exist one and only one type of
predefined stateless session bean, then things would have been different :-)
Regards,
Hemant
www.pramati.com
----- Original Message -----
From: "Dave Ford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 27, 2001 9:22 AM
Subject: Home for Stateless Session Beans?
What is the point of requiring a home interface for stateless session beans?
Unless I'm mistaken, it will always look like this:
import java.rmi.RemoteException;
import javax.ejb.EJBHome;
import javax.ejb.CreateException;
public interface FooHome extends EJBHome{
public Foo create() throws RemoteException,CreateException;
}
Why must developers create something that is exactly the same every time? Is
this just an exercise in futility? Or a plot to keep code-generating-wizards
in business? Or am missing something?
Dave Ford
Smart Soft - The Java Training Company
http://www.smart-soft.com
===========================================================================
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".
