Hey,
well, I chose the second option: since session are facades, I grouped
related methods into a single session, so I have few sessions with some
method. Useful also to deploy only parts of a complex system. If the system
is simple, I guess one session is ok.
Just my 0.02$
Simon
> -----Original Message-----
From: Shahar Solomianik
[mailto:[EMAIL PROTECTED]]
Sent: marte> d� 9 gennaio 2001 18:03
To: [EMAIL PROTECTED]
Subject: [jBoss-Use> r] Design issue
Hi again. (I am very active lately...)
Now
that my > inheri> ted CMP entities work, I come to code the session(s) to
> manipulate them.
My question is :
All my sessions will be
stateless.
How shou> ld I split the methods to different session beans> , or
> shoul> > dnt I
split ?
I mean, why dont have one stateless
session
bean with many methods, or the
other option : some/many> session beans each containing > one/more methods
?
> (After all,
> the sessions are stateless)
>
> Shahar> .
>
>
>
>
> --
>
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
