Today, Mark Bernardinis ([EMAIL PROTECTED]) wrote:
> 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.
I suspect the problem with using one of the session (stateful, stateless)
beans is that they would expire on you. On the other hand, I don't see
that one MUST do database accesses from an entity bean. You decide
what to do when the bean changes state -- for a stateless bean, well,
there ain't much to do ;)
I suspect what you want is a bean-managed persistence entity bean.
Where you just happen to persist nothing at all. I don't see why
an EJB container should have any problem with that, it won't know
what you're doing. Access can be given to any client. Since the
entity bean concept assumes that there will be state, access is
serialized, but unless you're really hitting it hard hopefully that
will be no big deal.
Gary
> > 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
>
>
>
>
