Hi Manish,
"A screen wants to use the functionality / methods of more then one
State Less Session Bean." This according to me is not a good design.
Ideally these should be simple Java classes that are instantiated by a
session bean, called a Session façade or more precisely a Business
Delegate in this case.
(http://java.sun.com/blueprints/corej2eepatterns/Patterns/BusinessDelega
te.html)
You may use such Façade classes for other functioanlities too. But the
business logic should be coupled with these.
Regards
Jaise
-----Original Message-----
From: A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@(protected)
Sent: Monday, July 12, 2004 3:38 PM
To: J2EE-INTEREST@(protected)
Subject: regarding the Session Facade Pattern use.
Hi All,
My scenario is
A screen wants to use the functionality / methods of more then one State
Less Session Bean. So, can I make one more stateless session bean
(Facade Bean) to delegate the calls from client to the needed session
bean. But one more problem I have is that the beans which are required
are used by other screens also as a Remote Bean and not local bean.
So, can you please suggest what I should do.
Actually I need to reduce the network call and data base connection
overhead for the performance point of view.
Can, I make one bean with reduntant method so, that I need to only make
one netowrk call but this would not be a good design, because latter on
if some other screen require this type of functionality then I have to
make more reduntant func. beans.
Thanks in advance.
regards,
Manish Malhotra
========================================================================
===
To unsubscribe, send email to listserv@(protected)
body of the message "signoff J2EE-INTEREST". For general help, send
email to listserv@(protected)
"help".
===========================================================================
To unsubscribe, send email to listserv@(protected)
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected)".
