You can still use an entity bean to provide this functionality. Nothing in
the specification states that the persistent store has to be a database. So
design your bean to be a BMP entity bean, then handle the loading and saving
of your data in your ejbLoad and ejbStore methods. You can serialize the
object, and use a helper class to load it and save it. This should allow you
to do what you are looking to do. you could feasibly do the same thing in a
stateful session bean though, but you don't have synchronized access to the
object.
Al
>I don't want to do any database activity. I just want this Java Object to
be
>accessible as an EJB accessible by many different clients hosted by an
>Application Server. The object doesn't have to be stateful either.
>
>> 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
