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?