Hi,
I would call this a bad design, because performance is going to be a strong
issue!!! try rethinking your design to distribute the load on more than on
bean. In the mean time make the Session bean an entity bean and place your
logic there. If you need to store data, an entity bean is what you want. you
can allways find it if you hard-code the primary key and do a simple
findByPrimaryKey. But still I would strongly advise to rethink your design.
Burkhard
----- Original Message -----
From: "Jeff Anderson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 31, 2001 7:40 PM
Subject: RE: [JBoss-user] will a stateless session bean instance be existing
thru out !!
> Wrap the session bean in a java class that implements a singleton.
> Jeff
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Arunachalam_P
> Sent: May 31, 2001 11:40 AM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] will a stateless session bean instance be existing
> thru out !!
>
>
> hi,
> Firstly, is it possible to have one & only one instance of a stateless
> session bean? (there should always be minimum & maximum of only 1
instance)
> If it is possible to configure, in which file(s) should i specify that?
>
> In the current situation I've to store/update some values in the stateless
> session bean, which is accessed by all clients.
> Can i be assured that only that instance is used by the clients, &
neither
> new instance is created nor the existing instance is destroyed.
>
> thanx,
> Arun
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
