8, 2003 10:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Stateless session beans
The section germain to the original question is 7.11.8 (2.0 spec)
"Non-reentrant instances"
The container must ensure that only one thread can be executing
an instance at any time.
As far as a s
: Tuesday, January 28, 2003 10:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Stateless session beans
The section germain to the original question is 7.11.8 (2.0 spec)
"Non-reentrant instances"
The container must ensure that only one thread can be executing
an insta
o:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 7:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Stateless session beans
No. As per EJB spec..
But Yes,ur code _may_ work fine with JBoss.
Is Jboss not following EJB spec?
-Original Message-
From: Eric Jain [mailto:[EMAIL PROTECTED
Boss-user] Stateless session beans
No. As per EJB spec..
But Yes,ur code _may_ work fine with JBoss.
Is Jboss not following EJB spec?
-Original Message-
From: Eric Jain [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 10:45 PM
To: jboss-user
Subject: [JBoss-user] Stateless
with JBoss.
Is Jboss not following EJB spec?
-Original Message-
From: Eric Jain [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 10:45 PM
To: jboss-user
Subject: [JBoss-user] Stateless session beans
Are stateless session beans threadsafe, i.e does the following code behave
as exp
No. As per EJB spec..
But Yes,ur code _may_ work fine with JBoss.
Is Jboss not following EJB spec?
-Original Message-
From: Eric Jain [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 10:45 PM
To: jboss-user
Subject: [JBoss-user] Stateless session beans
Are stateless session
yes.
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Eric Jain
> Envoyé : lundi, 27 janvier 2003 18:15
> À : jboss-user
> Objet : [JBoss-user] Stateless session beans
>
>
> Are stateless session beans threadsafe, i.
Are stateless session beans threadsafe, i.e does the following code behave
as expected?
public class TestBean
implements SessionBean
{
private int tmp;
// should always return true
public boolean f()
{
tmp = 1;
boolean b = tmp == 1;
tmp = 0;
return
> from multiple
> > > > transactions to the same instance
> > >
> > > I am not sure that it means that instances of SLSB are reentrant.
> > (spec. 7-11-8)
> > >
> > >
> > > Maris
> > >
> > >
> > > &
essage-
> > From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 16, 2002 12:15 PM
> > To: jboss-user
> > Subject: [JBoss-user] stateless session beans cannot call
> > stateful session beans!!?
> >
> >
> > Hi,
> &
essy [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 16, 2002 12:15 PM
> To: jboss-user
> Subject: [JBoss-user] stateless session beans cannot call
> stateful session beans!!?
>
>
> Hi,
>
> I wonder if someone could clear up a problem for me. It seems that a
>
Hi,
I wonder if someone could clear up a problem for me. It seems that a
Stateless session bean cannot really use a Stateful session bean for
two reasons.
1. The stateless bean cannot call remove on the stateful, therefore can't
clean it up (see code below)
2. If the stateless bean holds o
Hi,
I at least don't understand what state you are referring to as necessary to
call external resources.
How is this different from doing some jdbc-sql in a stateless session bean?
Do you want to maintain a pool of "connections" to the corba resource?
Possibly you are looking for resource adapt
Hello.
This message is more of a design question, sorry if it doesn't belong to this list.
Stateless session beans are usually used to implement service-like features, such as a
CalculatorBean which might have functionality for doing certain kind of calculations.
The Staless session beans work
14 matches
Mail list logo
