It sounds like you're describing an entity bean more than a session
bean. An entity bean can be called by many clients although access
is serialized. And certainly the role of an entity bean is to
encapsulate data in a apparently-storage-mechanism-independent manner,
from the client's perspective...
How does the notion of a session play into what you want the bean
to do?
Gary
Mark Bernardinis ([EMAIL PROTECTED]) wrote:
>
> Requirements:
> An EJB to be Stateful
> Accessible by more than client
> Share the same data object and information
>
> Summarising the above information, I would like to have an EJB that can be
> called by many clients yet share the same underlying data within the bean.
> These clients may be another application running under Orion or a
> stand-alone application.
>
> Is this possible, and if it is, what special requirements do I need to meet.
> I have looked at SessionContext but does this have anything to do with it?
>
> Thanks in advance.
>
> Mark
>
>
>
