Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

stateful session bean dilemma

 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

A business delegate creates a stateful session bean and keeps it cached to be used throughout the user's session. It is passed to a remote facade. The stateful session bean is only used by EJB tier and cached at the client tier. For performance reasons, I want a local stateful session bean...but this can't happen if BD creates it remotely.

Is this correct? If so, how can I solve it?

Thanks in advance.

-Saha
 
wise owen
Ranch Hand
Posts: 2023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The business delegate is a client side design pattern. If you use local stateful bean then you client code and application server code will run on the same JVM machine. Why do you need a remote BD?
 
Keerthi P
Ranch Hand
Posts: 203
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It (the Business Delegate) is passed to a remote facade.


You may want to reconsider this design.
 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I am passing the SFSB reference (handle) to the remote SLSB.

-Saha
 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Keerthi P,

I've been looking at javaranch posts and examples on the internet. I now realize that I should redesign (not a big change) to have a SFSB as my remote facade. Its a bit of a change but in the end better. Although I've been working with J2EE for about 7 years(not as long with EJB), I've no experience with SFSB. Thanks for the enlightenment! I'm back on track!

-Saha
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic