Philippe,
thanks for your posting.
> It is not right to say that the container only gives the beans access to
> Transaction
> and security services. The role of the container is (for transactionnal
> aspects for example) to assures that an EJB method will be invoked
> in the right scope of transaction depending on the transaction
> attributes.
> It is the container that interacts with the transaction service
> to suspend client transaction and begin a new one. It gives also
> the bean access to the transaction service via the EJB context in case
> of session beans;
That's just what I thought with "gives access". Since my answer was intended
for a beginner, I did not want to go into details.
> > So every bean has it's own container? Strange, where is the distinction
> > between Container and Context then?
> No there is a container for one ejb-jar file or ejb-jar.xml in which
> you can describe several EJBs
Just my thought; that's why I asked. By the way, is this a JOnAS specific
detail, or does the spec force every container to only manage one jar? It
makes sense to have one application in one jar, but is this a must?
Thank you
Markus
----
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".
