Hi,
I have a requirement of two clients accessing the same EJB component.
I need the first client to update the data in the bean and second client
to access the data. Since I want the data to be held in the bean, I
can't go for a stateless bean and as also the data doesn't represent a
table data so I can't go for an entity bean.
So in this case is it a right thing to implement the above bean as a
stateful session bean. Initially I thought that I can't access the same
stateful session instance from two clients, but when I tested sending
the handle for the stateful session bean from the first client to the
second client I could access the same bean instance and access the data.
Is it the right thing to do?
Is there any other ways of doing the above thing?
TIA
Sujeevan Kalam
===========================================================================
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".
