• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

question about design of Stateless Session Bean?

 
Ranch Hand
Posts: 84
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi, I usually used session facade pattern with 1 stateless session bean as a controller interacting with several Entity Bean to realize business logic in usecase.

now, as business logic grows more complex, to promote component reuse, I'd like to add a common service layer between the controller stateless session bean and Entity Beans. Should I use stateless session beans for this kind of common service layer? I'm afraid that a transaction span across multiple stateless session beans would hurt performance?

anyone here could help me out?
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
No, just make the Service layer POJOs.

"1 stateless session bean as a controller interacting with several Entity Bean to realize business logic in usecase."

How big is that Session Bean? I would definitely stick that stuff in the Service layer like you plan.

Mark
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic