Thanks for your reply.
I thought about it a lot and below are my inputs
Let us consider the flow
BD - > SFSB(Session Facade) - > Entity Beans
In the above case
a) Session Facade(SFSB) will have more methods(not a good
idea)and one that will be difficult to maintain
b) This SFSB must have remote interface
c) The basic responsibility for a facade would be to
1) Manage worlflow
2)Manage conversational state
I decided to maintain session state in SFSB since it is J2EE blue prints best pratice. So the state is shifted to SFSB behind SLSB
d) I don't want to have say 4 SFSB as session facade based on modules(again considering the number of instance based on concurrent users) but would appreciate your valuable inputs, since i am
In the apporach
BD - SLSB(Session Facade) -> SFSB - > Entity Bean
As I stated there are 4 SLSB based on modules and all these are accessed via remote interface
The reson for having session facade as SLSB is based on the pet store approach but slightly different
In petstore Business Delegator calls processEvent method on EJBController thru it remote interface. EJBController calls corresponding EJBAction class. EJBAction class actually does the business processing(Work flow).
As i stated above Session Facade should
a) Manage workflow
So taking pet store approach does not jusity, since EJBAction class does the business processing(Work flow) whereas facade acts as factory
to call appropriate EJB Action class.
So I decided to go for SLSB (Session Facade)and as I said I have 4 Session Facade based on modules. The methods in this session Facade does business processing(Work Flow) calling SFSB and entity bean to accomplish task.
But regaring passivation and activation current App servers has the best approach to provide performance mananging SFSB instance utilized effectively. But even then ...
Let me know your thought guys