In some examples I have seen it is possible for one EJB to do a
InitialContext.lookup of another EJB as a normal client can. If this is
valid what is the point of the ejb-ref and ejb-link in the deployment
descriptor?
I ask this because it seems to me that an EJB server cannot be regarded
as an application server because there are too many restrictions on an
EJB instance to allow it to represent a large chunk of application. i.e.
No sockets, thread, file access.
If this is true I have been thinking about extending a Container or
adding Resource Factores to provide extra functionality for particular
types of bean but a bean has a very limited knowledge of it's container
or container capabilities.
What do othe people think?
bill
N.B. I haven't read the 2.0 spec.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
