Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Shopping cart strategy for part 2. JSF with session scope or Stateful Session Beans?

 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

My application is a web application which I chose to use JSF. Now, being that performance is a paramount requirement, would it be better to use a JSF managed bean with session scope or Stateful session beans to maintain conversational state with client?

I know that maintaining session state in stateful session beans is a BluePrints best practice, but aren't they too heavyweight when compared to HttpSession? Also, I've separated my web and EJB tiers to run on different servers and each server itself is clustered.. I know some web servers do provide HttpSession clustering, so I mentioned I'd be using one that could guarantee that.

Important notice: there's no mention of other non web applications (i.e. swing app) accessing the business tier of my application. This is very misleading when taking such decision.

Any comment will be greatly appreciated.

Best regards,
 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If there is no mention of non web clients, then go http session.
Since performance is paramount requirement, why don't you choose web ejb co-located architecture?
 
Rodrigo Cunha
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by wang andrew:
If there is no mention of non web clients, then go http session.
Since performance is paramount requirement, why don't you choose web ejb co-located architecture?



makes sense, and it�s surely something to think about.. the only thing is that I�ve already proposed a DMZ which is where I�d expose the web servers and have protected the application servers inside the internal network (behind the 2nd firewall). I�d probably have to change that..

I�ll study the advantages and drawbacks of this approach and see how feasible it would be. will let you know.

Thank you so much for the reply.. really appreciate it.

best regards,
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
if you need colocated architecture do you think that EJB is required?
 
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I remember having to go through the same set of questions

Here is what I considered to come to a conclusion

* If we maintain sessions in the HTTP session scope, how would a rich client maintain session

* What will be the impact on scalability and performance if stateful session beans are used.

I had to ponder on those two questions for a while before coming to a conclusion. Good luck with your design
 
Rodrigo Cunha
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by dhruboj kayal:
if you need colocated architecture do you think that EJB is required?



Unfortunately for reasons I can�t talk about.. yes.

Actually what is killing me here is that I need to keep track of user session, and doing so w/ Stateful session beans in a multi-tier approach may compromise performance (w/ lookups), that we could prevent with a co-located approach.

Now you might be thinking why not multi-tier and having HttpSession clustering for the web tier (since many vendors already provide it)? I strongly believe the test reviewers would be happier to see a solution with stateful session bean (which is blueprints recommendation when using EJBs) rathen then a solution with HttpSession clustering provided by a third party. But again, it�s just a guess.

Any comments?

Regards,
 
Rodrigo Cunha
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Deepak Bala:
I remember having to go through the same set of questions

Here is what I considered to come to a conclusion

* If we maintain sessions in the HTTP session scope, how would a rich client maintain session

* What will be the impact on scalability and performance if stateful session beans are used.

I had to ponder on those two questions for a while before coming to a conclusion. Good luck with your design



Thank you so much for such valuable reply

best regards
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic