This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
I am achitecting a mutitiered aplication with a ejb-layer, web app. layer with 2 controllers: one for browser clients and one for rich web clients. I am wondering about the benefits/minuses of the following designs: - having 3-4 SLSB as session facades/bus. delegates (like Cade book) - this is my current design - having SFSB instead (like Petstore)- blueprint best practice recomandation (stated at least 10 times on some pages ;-) - how each of these would integrate with the "proxy controller (web-app) - ejb controller (ejb)" strategy (like Petstore). Do I use one for each facade??? :roll: Please comment Rudi
You will need the two controllers no doubt since they handle two different clients and thus two different protocols are involved. However, you will only need SFSB if you must manage state for a client. Which doesn't seem like a requirement.