If you have to do some "pre-processing" for a cmp, you can do this in your
slsb versus a sfsb. See this link for the example use case, but it is
essentially when you are using an index key for the cmp, the most common key
for cmp. For example, if you need to swing in and out helper beans, you can
do this in the slsb without incurring the penalty most associated with the
sfsb. This way you can bind what is essentially a business method for
handling the cmp in a session bean, which is where it belongs. This way your
cmp is just about it's little world of indexes and member variables,
where-as your slsb can have a business method
*slsb.getMyContacts("elephantwalker")*, versus
1. some helper bean instanced in a jsp or servlet
*fatbean.getMyContacts("elephantwalker")*, where the fatbean doesn't take
advantage of any of the containers instancing, pooling and other resource
handlers used by the slsb.
2. Some sfsb where the helper beans are instanced and then stay around for
eternity eating up resources in the sfsb.
Brett has a good article on these ideas at flashline:
http://www.flashline.com/content/mclaughlin/current.jsp?sid=989183633781-109
0580543-153
regards,
the elephantwalker
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Frank Eggink
Sent: Sunday, May 06, 2001 1:44 PM
To: Orion-Interest
Subject: RE: custom finder in CMPs (SLSB facade)
Ummmm, this is a question which is burning for sometime now.
I certainly not intending to challenge, but I take this as an opportunity
to raise the question.
I understand the performance benefit of Stateless Session Beans (SLSB) over
Stateful Session Beans (SFSB): this benefit is caused by the fact that
pooling is easier for SLSBs.
Now the question:
How come so many people are keen on introducing SLSBs as a facade in front
of Entity Beans to improve the performance? The same code (plus a tid bit
extra) needs to be executed, the same pooling behavior is there for the
Entity Bean and yes the SLSB introduces little to no overhead, but I still
see no gain.
What benefits am I overlooking?
Pls. enlighten me,
FE
On Friday, May 04, 2001 6:24 PM, elephantwalker
[SMTP:[EMAIL PROTECTED]] wrote:
> Armin,
>
> Another pointer for Stateless Session beans is that they have very a
> goooooood performance profile. According to Brett McGloughlin, they can
be
> upto 1000 times faster than Stateful beans.
>
> Regards,
>
> the Elephantwalker
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter
> Pontbriand
> Sent: Friday, May 04, 2001 5:45 AM
> To: Orion-Interest
> Subject: Re: custom finder in CMPs
>
>
> Commonly, developers build a Stateless Session EJB "facade" through which
> all access to Entity EJBs is accomplished. If you were to employ such a
> pattern, the method of this "facade" that invokes the CMP finder in
question
> would be an appropriate place to manipulate the results before returning
> them to the client. Have a look around www.theserverside.com for lots of
> information and discussions of EJB module design.
>
> P.Pontbriand
> Canlink Interactive Technologies, Inc.
>
> ----- Original Message -----
> From: "Armin Michel" <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Sent: Friday, May 04, 2001 4:31 AM
> Subject: custom finder in CMPs
>
>
> > Hi.
> >
> > I want to add additional code to the finder-methods
> > (for further restrictions on the find-results based upon security
> > information).
> >
> > How can I achive this?
> > I'd like to extend those auto-generated finder-methods and don't want
to
> fall
> > back to BMPs.
> >
> > Hope someone can help.
> >
> > Armin Michel
> >
> >
>
>
>
