The call to a SFSB cause you (with Orion) at max the additional penalty of an extra
Activation and Passivation cycle. Depending on the amount of resource usage for
these extra cycli as percentage of the overall resource usage, the use of SFSBs will
hit you.
The thing which puzzles me is why not
IMHO, facades are only useful when they do some extra-work, e.g.
consolidating the work with many other EJBs.
When you just use a facade to plainly forward any request to exactly one
EntityBean (1:1 relationship between facades and EntityBeans) than it's not
worth the trouble.
I am just
Armin Michel wrote:
IMHO, facades are only useful when they do some extra-work, e.g.
consolidating the work with many other EJBs.
When you just use a facade to plainly forward any request to exactly one
EntityBean (1:1 relationship between facades and EntityBeans) than it's not
worth the
PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Armin Michel
Sent: Monday, May 07, 2001 8:32 PM
To: Orion-Interest
Subject: Re: FW: custom finder in CMPs (SLSB facade)
IMHO, facades are only useful when they do some extra-work, e.g.
consolidating the work with many other EJBs.
When you just
The thing which puzzles me is why not go to the Entity Bean directly itself? It saves
both computer and programming resources. In all discussions and readings I have
found no decent arguments that prevent me from going direct, unless you throw in
the -valid- information hiding argument.
Another important thing to consider is transactions. If you have several setX methods
that you want
to call on the entity bean, and their transaction type is required, then you either
have to handle
the transaction in your client or pass the transaction handling off to a SLSB by
making one
