It's a bad idea because what if in the future you want to use that
business logic elsewhere? What if you want to use it in a webservice or
in a GUI standalone application. The business logic should have to know
nothing about web servers and HttpSession objects, unless your business
is building web servers.
meena r wrote:
Hi,
We have been mulling over an issue where , we have
people on our team who are proposing to pass the
HttpSession which we have in our Action classes to the
buisness delegate(which is an ordinary java class
which encapusulates calls the session facade). While
the j2ee blueprint for the business delegate pattern
says that the delegate decouples client code from
buisness component usage and lookup, folks in the team
am working on believe that there is no strong reason
why the session should not be made available to the
delegate. Please pour forth any opinion as to whether
this is a wise thing to or not.
Thanks
Meena
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
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]
