Hello,

do not know much background, but H->BO->DAO solution seems OK when standalone (web)application. Consider using stateless session beans when you want to publish your business logic as remote RMI service to another application. Session handling in HTTP session is mostly OK.

Ago

Ranjeeth kumar wrote:

All-

I am in the process of designing a application and after much analysis
we came to a conclusion that we don't need Entity Bean,  since
transactions are off simple nature.  So we will be using
Helper->BO->DAO scenario.

One of my collegue suggested that we should still use Session Bean as
a session Facade in between HELPER and BO. I am not able to convince
myself. All our session handling is done by using HTTP session.

The only advantage I can think of in this scenario is if we need to
move the whole business logic ie. BO+DAO in a seperate server, it will
help . Other than this I couldn't find any advantage.

Ur comments will be really valuable in this case

-Ranjeeth

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com
  

--
Rohelist kevadet,


Ago Meister
Engineer,*Webmedia*

Narva Street 7D, Tallinn 10117, Estonia
gsm: +372 51 87 218
fax: +372 6 696 748
msn: meisterago@hotmail.com
skype: meisterago

ago.meister@webmedia.ee
http://www.webmedia.ee

==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com