This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am preparing for SCEA-Part II. In one scenario, I have sesion facade which is stateless session bean. Now I want to call another class from session facade to do the rest of task. What type of class should I create to help session facade and code rest of business logic. Should I go for statelss session bean or simple java class to code business logic? Please suggest.
I too have a similar question. Is there any advantage in having the business logic in POJO classes - does(or doesn't) that make the application light weight and hence perform and scale better ? Is (or isn't) it a good practice to reduce the number of EJBs?
Also, wont usage of POJO classes minimize the EJB-EJB call, yet give us the container capabilities that come with the usage of EJBs?
A few questions...this might help you decide what to do...
what are the benifits of having an EJB behind the facade layer?
Do you want to handle any transcations and security in this EJB or will you do it from facade layer?
Can you isolate your business logic into a POJO and use it as a statless service being called from the facade layer?
Is the information propagating out of POJO into another layer (Database, EIS etc)? Can this propagation be handled from the POJO in a statless manner (You mentioned scalability..do you want this layer to handle information in a stateless manner?)
For questions / discussions on the assignment, in general we will allow discussion where members are trying to understand the domain model and/or terms used in the assignment. We will also allow questions about which tools to use.
But we will not allow discussion on a solution to the assignment (or a part of the assignment) itself.