I've never had to do anything like this in practice but I took a course on
Weblogic a while back at BEA HQ in NJ and one of our exercises was to
serialize a handle to a bean to save it to a file and access that same
instance from another client by reading the handle.
Sort of the same thing. And if it wasn't important or useful why would they
teach it. ;)
Derek Clayton
Code Meister
www.iceinc.com
----- Original Message -----
From: "Kalam Sujeevan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 02, 2000 1:34 AM
Subject: sharing stateful session bean
> 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".
>
>
===========================================================================
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".
