So, what happens when someone says make your java application a web
application? You have too much logic in your java client. If it is in the
slsb, who cares what your using for the frontend system. Another scenario,
someone else wants to use your entity beans in your corporate enterprise.
The front door should be your slsb so you can control what they put in or
take out.
Lou Farho
Certes Solutions, Inc.
http://www.certes-solutions.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Frank Eggink
Sent: Monday, May 07, 2001 2:08 AM
To: Orion-Interest
Subject: FW: custom finder in CMPs (SLSB facade)
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 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.
The system I'm working on uses a Swing client. Most important reason: Using
an
application client you can validate user input the moment it gets entered.
One of the things we do is validating keys against the server the moment
someone
has entered the complete key. The validation is done against the Entity Bean
itself,
not against a facade.
Now I know that the quality of constructive comments does not necessarily
have a
positive correlation with the price of a suite, but an expensive (and thus
highly regarded)
consultant claimed that using a SLSB facade is better.
I still can't figure out why (although I do agree that the extra performance
overhead is little),
so I'm tending to the position that it's probably bollocks.
Stuborn at the risk to get shot ...
FE
