Basically, because of the performance issue. It takes a while to
initialize the facade with every single request.
What's the problem with this ?
Frank W. Zammetti wrote:
It may be OK, but my experience tells me its atypical... the question
I would ask is why you need to cache the reference to the facade in
the first place? Typically you get an instance of it, either a new
instance or a pooled instance from a JNDI lookup or some factory or
something along those lines for each use (usually one per request)...
is there something about the design of your facade that makes this not
possible, or are you thinking of performance reasons?
Frank
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
(2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
(2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
Mansour wrote:
Hello every one:
I am trying to access my business layer from Actions. However, I
need to hold a reference to the business layer facade and access it
from any Actions classes. I am saving the reference to servicesFacade
in a session and retrieving it in the Action. I am having no problem
with this, but I don't know if this is the proper way to do it. Is
there other alternatives ?
I need an advice.
Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
