On Thu, 1 Mar 2001 15:48:10 +0000, Ian McCallion
<[EMAIL PROTECTED]> wrote:
>Can you give us some idea of the problem you solved by having state associated
>with the entity context? Would I be right in thinking of things like socket
>connections, connections to legacy systems, or business rules loaded from a
>database are best associated with the entity (or session) context?
For my masters thesis we developed a mobile agent system using nothing
but J2EE. EntityBeans was used as a kind of container for mobile agents,
and the heavy operation was to set up an internal container environment
inside an EntityBean instance in which a mobile agent would "live". This
included services (made available through the BeanContext API) that
allowed the agent to interact with its surroundings.
At the time we used the Orion server, which did not support instance
pooling, so it was terribly slow only because of the overhead of the
setEntityContext operation.
Read more about it here:
http://www-und.ida.liu.se/~karbl058/saft/
regards,
Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
===========================================================================
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".
