Hi Andrew
Because that's what the spec' says.
Your original (A) session bean cannot tell the difference between a second
call being made by a loopback (as you describe) and a second call by the
client, so it rejects both. It's much safer that way and to be honest if
you're having to do that it suggests to me that your session beans have a
design flaw (too small is a possible one, or perhaps you should be
considering helper classes is another. Obviously without knowing anymore
detail, and no I can't analyse yours in detail - I have my own work ;-), I
can't say much more).
Edward
-----Original Message-----
From: Nortje, Andrew [mailto:[EMAIL PROTECTED]]
Sent: 04 January 2001 22:57
To: 'jBoss'
Subject: RE: [jBoss-User] Stateful Session Bean Call Back
Why?
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 04, 2001 4:24 PM
> To: jBoss
> Cc: 'jBoss'
> Subject: Re: [jBoss-User] Stateful Session Bean Call Back
>
>
>
> You should not call another stateful session bean from a
> stateful session
> bean, not to talk about call-backs.
>
> Thomas Kirsch
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
