> Thanks for all your answers. They were very helpful, but I think you're
> wrong on the container one. I checked the EJB Specs from Sun and it says
> this:
> The container runtime provides the deployed enterprise beans with
> transaction and security management [and other services - I ommitted] that
> are generally required as a part of a manageable server platform.
This is not different to what I thought (maybe I pointed out not good). The
container is providing this services to the bean, but it really only
provides it and does not run it. That means, there is a security and TX
server running (really only one instance for the whole J2EE server), and the
container only gives the bean access to it. So the container is not doing TX
or security services, it only looks for some, gets a handle, and forwards
that handle to the bean (as a context).
> It also draws a distinction between the "Container" and the "Server,"
which
> it states can have different providers.
Yes that's true, but for the interfaces between container and server are not
well defined, I do not know of any example where container X can run within
server Y. :-(
> As well, I looked at the source code
> of JOnAS and there a container is basically an implementation of the
> ejb-jar.xml for each bean (or ".jar") file. Every ".jar" or individual
bean
> (if not in a ".jar") has its own container, all of which can live in the
> same Server. There can also be multiple servers too.
So every bean has it's own container? Strange, where is the distinction
between Container and Context then?
> If you want more info
> on this, let me know and I'll point you to the actual source code.
Yes, if it's not too complex, please send filename and line number.
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
