 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | Using Session Bean as session facade | Using Session Bean as session facade 2005-03-29 - By Pavana_cherukuri
Back
Hi,
Here I feel you need to take a call based on scalability. How scalable
are you expecting your application to be. In case you are not expecting
functionalities/clients to get added (as you had already said you are designing
for simple transactions) I feel you can do with out EJB components also.
Regards,
Pavan
-- --Original Message-- --
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTERNS-INTEREST@(protected)]On Behalf Of Vijay K Dasari
Sent: Tuesday, March 29, 2005 8:02 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: Using Session Bean as session facade
Hi,
Helper -> BO -> DAO can be an alternative for Entity Beans.
But this pattern does not support distributed computing. That means other
applications
can not reuse the Business Services.
If we use Session Facades (Enterprise Javabean Components), any application
can use the business
services provided by the Facade interfaces.
By using Session Beans (Facade pattern) we can take the advantage of J2EE
application servers
capabilities like caching, performance tuning, distributed computing,
transactions and so on.
Vijay.
> -- --Original Message-- --
> From: An interest list for Sun Java Center J2EE Pattern Catalog
> [mailto:J2EEPATTERNS-INTEREST@(protected)]On Behalf Of Ranjeeth kumar
> Sent: Tuesday, March 29, 2005 6:40 AM
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: Using Session Bean as session facade
>
>
> 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@(protected)
===================================================================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@(protected)
===================================================================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@(protected)
|
|
|
