RE: Stateless Session Beans

ginal Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of SCOTT FARQUHAR > Sent: Thursday, May 03, 2001 3:48 PM > To: Orion-Interest > Subject: Stateless Session Beans > > > I'm hoping that someone can help me with this. > > Can you have

RE: Stateless Session Beans

Class"). You can also get a env reference, and let the slsb get the reference (if its a simple object you want). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SCOTT FARQUHAR Sent: Wednesday, May 02, 2001 10:48 PM To: Orion-Interest Subject: Statele

Stateless Session Beans

I'm hoping that someone can help me with this. Can you have a stateless session bean that actually has class variables? Ie I want to have a variable that is loaded once per application, and then accessed by all the whole application. I know that SLSB are pooled and created and destroyed at wil

RE: Stateless session beans reuse

to:[EMAIL PROTECTED]]On Behalf Of Jason Boehle > Sent: Wednesday, December 13, 2000 4:28 PM > To: Orion-Interest > Subject: RE: Stateless session beans reuse > > > My understanding is that the fields will not be set to null. Instance > variables are useful in stateless sessi

RE: Stateless session beans reuse

My understanding is that the fields will not be set to null. Instance variables are useful in stateless session beans to hold references to "global" objects/resources that are used over and over again. You can allocate/release the variables in ejb[Post]Create()/ejbRemove(). Pleas

Stateless session beans reuse

Stateless session beans are clearly allowed to have instance variables (fields). A client of a stateless session bean cannot assume that he has the same bean instance for each method call. Assume we have a stateless session bean, which holds some fields storing various home interfaces. Gary (my

Re: Home interfaces and stateless session beans

00, you wrote: >> >Sorry for the newbie question... >> > >> >In the business methods in my stateless session beans I've always done what >> >seems like the usual pattern - lookup and narrow entity bean home >> >interfaces in the method that uses

Re: Home interfaces and stateless session beans

, you wrote: >At 01:20 PM 10/11/00 -0400, you wrote: > >Sorry for the newbie question... > > > >In the business methods in my stateless session beans I've always done what > >seems like the usual pattern - lookup and narrow entity bean home > >interfaces in the me

RE: Home interfaces and stateless session beans

I do that right now with no problems yet. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of KirkYarina > Sent: Wednesday, October 11, 2000 1:21 PM > To: Orion-Interest > Subject: Home interfaces and stateless session beans >

Re: Home interfaces and stateless session beans

At 01:20 PM 10/11/00 -0400, you wrote: >Sorry for the newbie question... > >In the business methods in my stateless session beans I've always done what >seems like the usual pattern - lookup and narrow entity bean home >interfaces in the method that uses them. However, to

Home interfaces and stateless session beans

Sorry for the newbie question... In the business methods in my stateless session beans I've always done what seems like the usual pattern - lookup and narrow entity bean home interfaces in the method that uses them. However, to save some time, I'd like to do these lookups in

Pooling stateless session beans

I wonder if it is possible to affect how the OrionServer pools stateless session beans? Can I configure it so e.g. that OrionServer always keeps 5 stateless session beans ready to serve clients. Now when I create and call a method in a stateless session bean, OrionServer creates and keeps one

Stateless Session Beans

It seems (at least on version 0.8.3) that stateless session beans do not act as "real" stateless session beans. In "Enterprise JavaBeans" (Monson-Haefel, O'Reilly, p. 189-190) stateless session beans are said to be created by the container and not buy the client. "

RE: Creation of stateless session beans

rom: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Juha Lehtonen > Sent: Monday, January 31, 2000 3:53 PM > To: Orion-Interest > Subject: Creation of stateless session beans > > > I am using a stateless session bean, > which should according to EJB specs > be po

Creation of stateless session beans

ooled instance of an old bean. How can I configure the Orion server to handle the stateless session beans so that the number of new bean instances will stay to its minimal? Juha

bugreport: stateless session beans not spec compliant

Hi, I think there are two bugs in the stateless session bean implementation. 1.) as far as I understand 6.8.1 of the spec the container has to invoke "setSessionContext" and "ejbCreate" on stateless session bean instances before they are ready to serve client requests. this doesn't happen in

session timeout on stateless session beans, why?

Hi, I'm getting session timeouts on stateless session beans. I thought that timeouts only made sense on stateful session beans? Could someone please clarify that? The state diagram of stateful session beans contains a timeout but the one for stateless session beans doesn't. Am I misin